Update UseResourceIdFunctionsRule to account for nullable and aggregate types #12421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #12419
The
UseResourceIdFunctionsRule
linter rule doesn't report any diagnostics if a parameter is supplied for a resource property that expects a resource ID, but this exemption doesn't apply directly to parameter properties. This didn't raise any issues in the past because prior to the introduction of user-defined types, parameter properties would always have anany
type, and the linter rule will only raise diagnostics onstring
-typed values.Microsoft Reviewers: Open in CodeFlow