Having a means of collecting more targeted and easy-to-triage type issues

[anthony-c-martin]

It's getting pretty hard to look through and triage #784 with the volume of comments coming through.

It might be worth thinking about a way to collect more targeted feedback - e.g. a form with fields like:

• Resource Type
• Property Path
• Issue Type (dropdown here)
• Other Comments

EDIT: I've created an issue template here: https://github.com/Azure/bicep-types-az/issues/new?assignees=&labels=inaccuracy&template=types_inaccuracy.yml

We should be able to generate a link to it programmatically within Bicep, with some fields even filled out - e.g.:

https://github.com/Azure/bicep-types-az/issues/new?template=types_inaccuracy.yml&title=[Microsoft.Compute%2FvirtualMachines%202020-01-01]%20Azure%20types%20inaccuracy&resourceType=Microsoft.Compute%2FvirtualMachines&apiVersion=2020-01-01&repro=bicep%0Aresource%20foo%20%27Microsoft.Compute/virtualMachines@2020-01-01%27%20=%20{%0A%20%20...%0A}%0A

[alex-frankel]

Connected to #6206

[anthony-c-martin]

Did some experimentation on this branch.

It's possible to write a code action which opens a URL if invoked - this works pretty nicely and feels like a viable approach. Here's a demo with my VSCode & browser window side by side. As you can see, most of the fields in the issue report are pre-filled with data from the resource I have selected:

https://user-images.githubusercontent.com/38542602/194199097-78655b6f-70ea-4745-ac29-907481d6615d.mov

[majastrz]

This is really cool!

[alex-frankel]

I assume it is ok if two issues have the exact same title? Would be cool if we can have automation that identifies and auto-closes duplicates.