-
Couldn't load subscription status.
- Fork 699
Refine TypeCollector usage and predicates
#3363
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
Conversation
TypeCollectorTypeCollector usage and predicates
| * @author Mark Paluch | ||
| * @since 4.0 | ||
| */ | ||
| public interface TypeCollectorPredicateProvider { |
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.
What if we renamed this to TypeCollectorPredicates?
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.
a bit confusing, naming it predicates, TypeCollectorFilterProvider maybe?
We now provide a SPI for libraries that want to provide predicates for AOT processing so that AOT processing not only considers its own rules but also e.g. exclusions from other participants on the class path.
Rename TypeCollectorPredicateProvider -> TypeCollectorFilters Update javadoc and deprecate jpa specific predicate.
76cceef to
14caf37
Compare
Rename TypeCollectorPredicateProvider -> TypeCollectorFilters Update javadoc and deprecate jpa specific predicate. Original Pull Request: #3363
Make predicates on
TypeCollectorusable, introduce strategy interface so that AOT participants can contribute their own predicates for inclusion/exclusion of types that should be considered reachable.