Fix cut annotations JDT issue #103
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
Not sure why, but it seems cut annotations can't handle single annotations with eclipse
|
I think it happens because jdt keeps the whitespace between annotation attributes |
rbygrave
approved these changes
Mar 14, 2025
rbygrave
added a commit
to avaje/avaje-validator
that referenced
this pull request
Mar 15, 2025
Relis on avaje/avaje-prisms#103 Co-authored-by: Rob Bygrave <[email protected]>
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.
Not sure why, but it seems cut annotations can't handle single annotations with eclipse.
Checklist before merge
Have these changes been tested with the below to confirm no negative interactions?