microsoft / microsoft/vscode-azurefunctions
Cosmos Trigger Prompts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 319
- Forks
- 158
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 4
Description
When creating a Cosmos trigger I'm given the option of selecting the Subscription and I get a list of subscriptions, but from there I have to type in the account, database, and collection. why can't we show these in a quick pick, like when i set a connection to Cosmos from the App Service extension?
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 Cosmos trigger creation flow and compare it with the App Service extension's Cosmos connection quick-pick flow shown in the issue. Done means the trigger setup can select the account, database, and collection from quick picks after selecting a subscription; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100