-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Check for DisplayNameGeneration annotations on runtime enclosing types #4268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
marcphilipp
merged 8 commits into
main
from
marc/4131-runtime-enclosing-types-annotation-lookup
Jan 27, 2025
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c2bfe37
Deprecate `SearchOption` and related method and introduce replacement
marcphilipp 42022f9
Check for DisplayNameGeneration annotations on runtime enclosing types
marcphilipp 4d05f53
Fix typo
marcphilipp 87ef69d
Improve Javadoc
marcphilipp ee7be46
Restore accidentally removed blank line
marcphilipp da61c32
Make method private again
marcphilipp b7237a8
Add release note entry
marcphilipp ea54233
Merge branch 'main' into marc/4131-runtime-enclosing-types-annotation…
marcphilipp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I certainly agree with that sentiment, developers and libraries that use
AnnotationSupportoften will not have access to the runtime enclosing types. Typically only JUnit internals have access to those.So, I am a bit reluctant to deprecate this feature.
However, if we deprecate it and nobody complains, then I suppose it's fine. 😇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jupiter extension authors can access them via
ExtensionContext.getRequiredTestClass(), recursively, or get them fromExtensionContext.getRequiredTestInstances()by callingObject.getClass()on each instance.I checked the original issue and didn't find an actual user request. Therefore, since this was the only place we used it, I deprecated the method. We can always undeprecate it if anyone complains. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also considered the fact that Jupiter extension authors have a way to access that information, so I was thinking more about the general purpose nature of the utilities in
AnnotationSupportfor other testing frameworks, engines, etc.Yep, as I mentioned before.... if nobody complains, it's fine. 👍