fix: Fixed nested UDT resolution if array definition is in parameter, not the type - Githubissues

Azure / bicep-registry-modules

Bicep registry modules

MIT License

399 stars 269 forks source link

fix: Fixed nested UDT resolution if array definition is in parameter, not the type #1970

Closed AlexanderSehr closed 4 weeks ago

AlexanderSehr commented 1 month ago

Description

Fixed nested UDT resolution if array definition is in parameter, not the type

This is now supported
```
param test myArrayType[]

type myArrayType = { ... }
```
Before it was only
```
param test myArrayType

type myArrayType = { ... }[]
```
Updated how the Set-ModuleReadMe script throws errors in case a cateogory is missing.
Fixed incorrect parameter metadata for a module
Re-ran generation for ALL modules

Pipeline Reference

Pipeline

Type of Change

[x] Update to CI Environment or utlities (Non-module effecting changes)
[ ] Azure Verified Module updates:
- [x] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
- [ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
- [ ] The bug was found by the module author, and no one has opened an issue to report it yet.
- [ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
- [ ] Breaking changes and I have bumped the MAJOR version in version.json.
- [ ] Update to documentation

microsoft-github-policy-service[bot] commented 1 month ago

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[!NOTE] This label was added as per ITA06.