custom platforms and aspects
Open
Nobody has claimed this yet.
🐛 bug
🐶 dogfood
👠 platforms
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
I tried this:
using an aspect from a relatively required platform, see here for an example with test cases
https://github.com/skorfmann/wing-custom-platform-aspect
This happened:
aspect is not invoked
I expected this:
aspect to be invoked
Is there a workaround?
require aspect from main entry point
Anything else?
No response
Wing Version
0.51.12
Node.js Version
18.7
Platform(s)
MacOS
Community Notes
- 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.
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 with the reproduction and test cases in https://github.com/skorfmann/wing-custom-platform-aspect, then trace how relatively required platforms load and invoke aspects. Done means the example's aspect is invoked without requiring it from the main entry point; the issue names no Wing source file or test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100