linkedin / linkedin/icon-magic
Explore making plugins streaming
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Within plugin-manager, we need wait for all the results of the first plugin before applying the next plugin. The output of each plugin results in one or more assets and all these assets serve as the input for the next plugin. We won't be able to achieve true asynchrony here unless we have a stream of sorts.
Contributor guide
No contributing guide indexed for this repository
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 reading the plugin-manager entry point and tracing how one plugin's assets become the next plugin's input. The issue does not name files, tests, or a completion condition, so clarify the desired streaming behavior and acceptance criteria before attempting implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100