support a multi-* declaration (should support params, outputs at least, but likely more)
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 79
Description
Parameters probably should always be declared at the top of the file anyway, and this should help with readability and terse-ness:
```
parameters {
prefix string = 'my string'
suffix string {
secure: 'true'
}
ipRange object {
defaultValue: {
myProp: 'my value'
}
}
}
```
would be nice if I can separate over multiple-lines:
```
parameters {
prefix string = 'my string'
suffix string {
secure: 'true'
}
ipRange object {
defaultValue: {
myProp: 'my value'
}
}
}
```
Contributor guide
Research direction
Start by examining the existing declaration syntax and parsing behavior for single parameters and outputs. Use the examples in the issue to determine how multiple declarations, nested object values, defaults, and blank lines should be accepted. Done means the requested multi-parameter form parses consistently, with equivalent support for outputs or other declarations agreed by the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100