We should get rid of the "resource-{,without-}defaults" and "resource-child-{,without-}defaults" snippets
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
We should check telemetry, but I'm guessing these are rarely used. I think we should at least get rid of the "without-defaults" versions.
1) Now that we have lots of resource snippets, I think these just clutter up the namespace and cause confusion:
2) They're not really useful (esp the without-defaults ones), you can just type "resource" and use intellisense
3) They lead you away from the better intellisense experience of having properties automatically filled out from the actual resource type once you've selected it:
Contributor guide
Research direction
Start by locating the resource-{,without-}defaults and resource-child-{,without-}defaults snippets in the Bicep repository, then check the issue's suggested telemetry before deciding the removal scope. Done means the agreed snippets are removed without leaving confusing or broken resource completion behavior; the issue names no tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100