Azure / Azure/bicep

Linter rule to enforce "strict" keyword order

Open
#6,602 3 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue story: linter rules story: registry
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

Params and outputs should be grouped together, params should be at the top, outputs should either be underneath params or at the bottom of the file.

Open question whether this should also enforce strict ordering of `module`, `resource`, or `var`.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. First clarify whether ordering applies only to params and outputs or also to module, resource, and var; done means the linter consistently enforces the agreed ordering.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.