microsoft / microsoft/vscode-azurecontainerapps
`pickItem` calls should only utilize one wizard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 21
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
A few of our pickItem wizards rely on first running a wizard to get the base ContainerAppItem. This means that two wizards are sometimes run back to back, and we lose the back button functionality between the wizards. To improve the back button continuity for our users, we should go back and fix it so that all pick steps are run in one wizard.
For additional reference: https://github.com/microsoft/vscode-azurecontainerapps/pull/778#discussion_r1859024316
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 locating the pickItem wizard implementations and reviewing the discussion in pull request 778. Identify pick steps that launch a second wizard after obtaining a ContainerAppItem. Done means all pick steps run within one wizard and preserve back-button continuity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100