redhat-developer / redhat-developer/vscode-quarkus
Wizard should cache the extensions list within the project creation workflow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
When creating a new Quarkus project, if you reach the extensions picker, the wizard fetches the extensions list per the selected platform. Now if you go back one step to change something, then reach the extension picker once more, a new http query is performed, which should not be necessary at that point. Within a single project creation workflow, extensions should be cached per platform, so as to avoid unnecessary http roundtrips.
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 at the project creation workflow's extensions picker and trace where the extensions list is fetched for the selected platform. Confirm the workflow can reuse a previously fetched list when returning to the picker, while fetching separately for other platforms. Done means repeated navigation within one workflow no longer causes an unnecessary HTTP request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100