Having a means of collecting more targeted and easy-to-triage type issues
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
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```
Contributor guide
Research direction
Start by reading the linked issue template in bicep-types-az and the feedback collected in #784. Determine how Bicep could generate a prefilled link with the listed fields and reproduction example; done means targeted feedback can be submitted through the template instead of adding comments to #784.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100