microsoft / microsoft/vscode-azurestaticwebapps
Hot reload Functions Host when new trigger is added
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 99
- Forks
- 39
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
@simonaco Mentioned from the customer study that there was an expectation that the new trigger shouldn't have to re-run the project when adding a trigger to a local project that is currently debugging. We should be able to hot-reload the project for them. With Mac, keep this workaround in mind: https://github.com/Azure/azure-functions-core-tools/issues/1738#issuecomment-622553961
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 tracing how the VS Code extension starts the local Functions Host and responds when a trigger is added during debugging. Read the linked Azure Functions Core Tools workaround, including its Mac considerations. Done means a new trigger is available without rerunning the project, while preserving the documented Mac behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100