microsoft / microsoft/vscode-azurefunctions
Ensure entities specified by user during trigger creation exist
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 319
- Forks
- 158
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 4
Description
Applies to Event Hub, Service Bus queue, Service Bus topic, and Cosmos triggers:
Users are prompted for info about the entity (event hub name, service bus queue name, topic/subscription name, Cosmos database and collection name), but these entities are not created for the user in the background, except strangely for the Cosmos database. If these specified entities don't exist, the follow exceptions are thrown during debugging (blocks of text that are hard to read - I took out the relevant sections):
Request:
- Auto create entity in background if not already exist. OR
- Leave comment in template telling users to ensure their referred entities exist before running code.
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
Review the creation paths for Event Hub, Service Bus queue/topic, and Cosmos triggers; the issue names no files, tests, or entry points. First resolve whether the intended outcome is automatic entity creation or a template comment, then verify that the chosen behavior prevents the reported debugging exceptions for each listed trigger type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100