Fix: @VerifyOnly now working as expected #6297
Merged
Conversation
This file contains hidden or 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
keyboardDrummer
approved these changes
Jul 3, 2025
|
I couldn't find how this change was tested, but in any case I think it's an improvement. |
|
The change was tested by migrating the existing integration and auditor tests for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #6146
@VerifyOnlywas creating an{:only}attribute instead ofUserSuppliedAttribute, which prevented from being detected as well as not retaining the origin.What was changed?
Changed detection of
{:only}to be any attribute, not just user-supplied.How has this been tested?
Migrated all tests to support the new
@VerifyOnlysyntax.Existing tests were updated.
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.