Wing examples: organize all test files based on the language spec structure
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
Community Note
Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
Feature Spec
Wing examples folder is now organized based on the language spec's structure.
Use Cases
We want to make it very easy to understand what is supported and how to use it. This structure should assist both Wing users and contributors
Implementation Notes
This should be easy to do at this point, while we have merely a few examples.
We should also add support for sub-folders under https://github.com/winglang/wing/tree/main/examples/tests/valid and https://github.com/winglang/wing/tree/main/examples/tests/invalid - this can be done in the hangar tool
Component
Contributor Experience
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the examples folder with the language spec structure, then inspect examples/tests/valid, examples/tests/invalid, and tools/hangar/src/cli.test.ts. Organize the examples accordingly and add hangar support for subfolders under the valid and invalid test directories; done means the structure is easy to navigate and the hangar tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100