You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new RuntimeHints API allows to describe hints for the reflection/proxies/resources needs at runtime.
The problem is, a single invocation at runtime can be covered by multiple, different hints.
For example, reflection introspection on the myMethod method for the class MyClass can be covered by any of:
MemberCategory.INTROSPECT_PUBLIC_METHODS if myMethod is public
MemberCategory.INVOKE_PUBLIC_METHODS if myMethod is public
MemberCategory.INTROSPECT_DECLARED_METHODS in all cases
MemberCategory.INVOKE_DECLARED_METHODS in all cases
a specific introspection or invokation reflection entry for MyClass::myMethod
Because of the knowledge required for checking if registered hints are enough for a particular use case, we should introduce Predicate<RuntimeHints> static utilities to be used in tests and in #27981
The text was updated successfully, but these errors were encountered:
As of #28620, `ResourcePatternHint` exposes its `toRegex` method.
The predicates should use it directly and mirror the exact matching
behavior.
See gh-28555
The new
RuntimeHints
API allows to describe hints for the reflection/proxies/resources needs at runtime.The problem is, a single invocation at runtime can be covered by multiple, different hints.
For example, reflection introspection on the
myMethod
method for the classMyClass
can be covered by any of:MemberCategory.INTROSPECT_PUBLIC_METHODS
ifmyMethod
is publicMemberCategory.INVOKE_PUBLIC_METHODS
ifmyMethod
is publicMemberCategory.INTROSPECT_DECLARED_METHODS
in all casesMemberCategory.INVOKE_DECLARED_METHODS
in all casesMyClass::myMethod
Because of the knowledge required for checking if registered hints are enough for a particular use case, we should introduce
Predicate<RuntimeHints>
static utilities to be used in tests and in #27981The text was updated successfully, but these errors were encountered: