[Do not merge] Proof of concept of menu based CS creation#26
[Do not merge] Proof of concept of menu based CS creation#26nima-ap-zz wants to merge 2 commits intomainfrom
Conversation
|
I think I'd like to see all 3 options side-by-side so we can play with them and see which ones feel better, both in terms of experience and in terms of consistency with other extensions/snippets/commands in VS Code or extensions our developers will likely be using.
|
The first option is already completed and ready to test out. The second option would pretty much involve asking every question in the template from the developer in a squence of quickpicks/inputboxes which is equal to what Azure Functions Extension does today. The question for that model can be whether we are interested in providing a 'hello-world' like how AF function creation does, or if we're more interested in providing a 'here's everything you need to start writing a function over >here<' approach. Both are valid, and worth considering, however I would like to ask to be assigned to implement option 2 only if we are actually deciding to do it since it would require additional work for something we know what it looks like cause that's what azure functions are doing right now, in a private preview sprint for a feature not included in private preview. |
This PR demonstrates some of the options we have with regards to the 'create new cloudscript' action.
At its core, it simply creates a file and programmatically inserts a snippet for the user which they can from there onward tab to complete.
Please comment if need be so we can further discuss the options here cause we do have the option of doing everything like the Azure Functions extension as well.