some general ideas top of my head

[Adam-it]

hi 👋
For starters awesome work 🤩 and I am already in love with this extension 👏.
While playing around with it I have a looooot of ideas and I thought that instead of creating separate issues for each of those and making a mess in the issues list (sorry if I already did 😉🙏) I will create this one single issue with all of the ideas I currently have and you may decide on your own which are valuable and which totally are out of scope and make no sense at all 😅.

1. validate setup - I was wondering if the extension could have a kind of valdiate devproxy setup VS Code command. So when executed it would check in the user preferable terminal (based on VSCode settings) if devproxy (for example devproxy --help) works and is recognizable. If no the extension could present a notify that your devproxy is not properly setup with a button that when clicked would check if user is on win or mac and what shell and would run the install script for the user like (Invoke-WebRequest https://aka.ms/devproxy/setup.ps1).Content | Invoke-Expression in the console. If yes the extension could also present a notify that you are ready to go. Depending on how far this extension would go if in future it would extend VS code with some UI this command may be 'attached' to any button, like in the extension welcome experience to a button like 'validate your devproxy setup'. To provide an example I would say this could be a similar feature like the viva toolkit validates if the user has correct dependencies installed to start doing SPFx development https://github.com/pnp/vscode-viva/wiki/5.1-Validate-and-set-up-a-local-workspace

2. samples/presets gallery - I was thinking that the extension could have a command like open samples gallery that would open a dedicated webview in the editor window presenting all the dev proxy samples/presets from the pnp repo https://github.com/pnp/proxy-samples. The user should be able to get quick details about each sample, go to github repo or download it locally to the current workspace with a single click all without leaving VS Code. nowadays it became a quite common feature, for example Teams Toolkit has it's samples gallery, or PnP PS extension or Viva Toolkit as well

3. add a quick action to run devproxy with a mock - add a editor action to the toolbar visible when someone has a mock json file opened in the editor. The action should allow to run the devproxy command in the console with the currently opened mock.

4. add a command to start devproxy - this is probably and overkill but I was wondering if it worth having VS Code commands that will start devprox with a specific setting. For example the extension could have a command like run devproxy and record. After running it the extension would ask the user additional questions like "provide file name for the summary report (default empty)" and after that VS Code could run the command devproxy --record --summary-file-path report.md in the user console

5. add an icon to the status bar that would indicate if the proxy is working or not - this might be tricky as I am not sure how to do that just now 😅 I would need to do a bit of research 😉.

Ok this is just some ideas I had, I have some other ideas as well but those base on a concept that the VS Code extension would have some UI 🤔. I hope this will be of any help

Cheers 👍

BTW before I will be the person that just adds a lot of feedback and then doesn't provide any help at all 😅 I am wondering if you consider to be open for contributions? I would love to help out

[garrytrinder]

Awesome suggestions @Adam-it thank you for taking the time to share your ideas ❤️

I can say that for all of the things you've raised, I've had similar thoughts, but not added the issues for each and then prioritise them 😅

Let's break this up into individual issues and take it from there.

I am wondering if you consider to be open for contributions? I would love to help out

Absolutely!

[Adam-it]

That's awesome, I would love help out. For example the sample gallery 🤩

Should I open issues for each of those ideas? Or will you pick those that are promising and would like to add and then I will check what issue could I take?

[garrytrinder]

Leave creating the issues to me 👍

I've got some things that I want to put in place so its easier for contributing, for example, e2e tests of the current functionality so we don't break things going forwards, branch policies and some automation for releases.

[Adam-it]

Sure, when you have some issue ready for 'others' be sure to ping me up 👍🙂