microsoft / microsoft/vscode-azurestaticwebapps
Add additional checking for Azure Functions restrictions in Static Web Apps
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 99
- Forks
- 39
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
Currently, there are some restrictions for Static Web Apps functions that are beyond those of regular function apps.
- Core Tools should be the latest v3 version
- Only Node 12, .NET 3.1, and Python 3.8 are supported
- Only HTTP triggers are supported
- Only valid routePrefix in host.json is
api - It's not good practice to nest the API folder inside the web app. Not sure if we want to have a warning here. There's potential for exposing the API code if it's deployed as static files too, and npm modules in the function app can cause the static app to exceed the 4000 file limit
Internal tracking link: https://dev.azure.com/azuretracking/Azure%20tracking/_workitems/edit/1678
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 Static Web Apps Azure Functions validation entry point and reviewing how existing checks are reported. Compare the current behavior with the listed Core Tools, runtime, trigger, and host.json routePrefix restrictions, and decide how the API-folder concern should be handled. Done means the supported restrictions are checked consistently and the intended warning behavior is defined.
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
- 38/100