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
We got some feedback in #28977 that led us to reconsider some of the constructs in ReflectionHints and friends. Looking at the usage we've decided to:
Limit the ExecutableMode to a single value, with the ability to determine if a user-provided value is relevant or if it's already included in the configured one
Provide consistent registration methods that allows to set the ExecutableMode without having to customize the builder
Make sure that methods that do not take a builder and those who take one without mutating it generate consistent hints
The text was updated successfully, but these errors were encountered:
This commit harmonizes the registration of an executable so that
the default method and the method that takes an empty customizer
produces the same hint. The same applies to the readable flag of
a field hint.
Rather than returning a list of executable modes, the "highest" mode
is retained.
See gh-29011
This commit adapts the registration of fields, constructors, and methods
to provide the same convenience than the reflection-based one available
in ReflectionHints.
See gh-29011
Add `MemberCategory` and `FieldMode` shortcuts for type registration.
Helper `builtWith` methods have also been extracted to the Hint types
to allow general reuse (for example with `registerTypes`).
See gh-29011
We got some feedback in #28977 that led us to reconsider some of the constructs in
ReflectionHints
and friends. Looking at the usage we've decided to:ExecutableMode
to a single value, with the ability to determine if a user-provided value is relevant or if it's already included in the configured oneExecutableMode
without having to customize the builderThe text was updated successfully, but these errors were encountered: