Raise diagnostic when whole resource body is used as a type #13494
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9767ddb
to
7a4e53a
Compare
|
Test this change out locally with the following install scripts (Action run 8097736372) VSCode
Azure CLI
|
Test Results 66 files 66 suites 22m 48s ⏱️ Results for commit 3ea63e8. ♻️ This comment has been updated with latest results. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #13492
Ran into this error when working on reconciling resource-typed parameters and resource-derived types. I'd like to continue blocking using the whole resource body as a type until we figure out how to make those two experimental features work well together, but it should be blocked with an error diagnostic rather than just crashing the VS Code extension. 😅
Microsoft Reviewers: Open in CodeFlow