Azure / Azure/bicep

Autofix for any "use param instead" linter warnings

Open
#5,714 0 comments 0 reactions 0 assignees View on GitHub
devdiv enhancement story: linter rules
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

There are many situations in which this piece of advice shows up, but none where we give the user a quick click to fix the issue and continue authoring the bicep file.

Example when a user uses an aksCluster resource tab completion
![image](https://user-images.githubusercontent.com/20650058/150849672-d13229a3-f6de-4b9e-9af3-d8a6ed58c91e.png)

It would be great if we simply took the property and made a param with it at the top of the bicep file
![image](https://user-images.githubusercontent.com/20650058/150850456-58027cf6-1484-4256-be17-18f8e67fef9a.png)

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Start by locating the linter diagnostic for "use param instead" and its language-service code action handling. Define how the property becomes a parameter at the top of the Bicep file, then add coverage for the AKS cluster completion example and other occurrences.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.