This changes the Functions UI a bit to match what we discussed offline and insights from user studies.
Go back to removing Create New Project.... Replace Create Function... with Create function locally... (Not sure what looks best in terms of casing)
If you're unfamiliar, Create Function... handles the following scenarios:
Local project exists? Add a new function template.
Local project exists but it's not initialized for VS Code? Prompts user to initialize for VS Code.
Local project doesn't exist? Create a new project and ask what function template user wants (option to skip)
Added two entry points to Create function locally.... One on the Functions node indicated by the Function + button. Another as a context menu action. I'm debating moving it to the local project node.
Mentioned renaming Create Function... but also renamed Deploy to Function App in Azure... to Deploy function to Azure.... It makes more intuitive sense because your local project is being deployed to Azure, and we have to prompt for which app is being deployed to.
By that logic, I've kept Deploy to Function App... the same in the Resources view though.
Added Create New Project... to workspace view if there's no project in the workspace. It actually does call azureFunctions.createNewProject because we know that we need to start from scratch. createFunction has to do some checks before it ultimately cancels and calls createNewProject so performance is slightly better to just call it directly.
Removed Create Function App... option in the local workspace view
This was replaced with just Deploy function to Azure... which includes a + Create new function app option as a quick pick when we prompt for the app
Merged Create New Containerized Project... into Create function locally... and add it as a prompt at the beginning. It's annoying, but also a one-time cost to the user that can be easily entered through.
nturinski
commented
5 months ago
This changes the Functions UI a bit to match what we discussed offline and insights from user studies.
Go back to removing
Create New Project.... ReplaceCreate Function...withCreate function locally...(Not sure what looks best in terms of casing) If you're unfamiliar,Create Function...handles the following scenarios:Added two entry points to
Create function locally.... One on theFunctionsnode indicated by the Function + button. Another as a context menu action. I'm debating moving it to the local project node.Mentioned renaming
Create Function...but also renamedDeploy to Function App in Azure...toDeploy function to Azure.... It makes more intuitive sense because your local project is being deployed to Azure, and we have to prompt for which app is being deployed to.By that logic, I've kept
Deploy to Function App...the same in theResourcesview though.Added
Create New Project...to workspace view if there's no project in the workspace. It actually does callazureFunctions.createNewProjectbecause we know that we need to start from scratch.createFunctionhas to do some checks before it ultimately cancels and callscreateNewProjectso performance is slightly better to just call it directly.Removed
Create Function App...option in the local workspace viewDeploy function to Azure...which includes a+ Create new function appoption as a quick pick when we prompt for the appMerged
Create New Containerized Project...intoCreate function locally...and add it as a prompt at the beginning. It's annoying, but also a one-time cost to the user that can be easily entered through.