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
TestHelpers contains a bunch of useful methods to easily create FieldResolverStrategy instances for a single resolution, e.g., for a specific value, or using a Supplier. Recently I've wanted a few of these in production code. So, create a new utility/factory class that contains methods to easily create instances when you only want a single strategy.
It could be named FieldResolverStrategies and provide all or only a few of methods that exist in TestHelpers currently. Here are the signatures from TestHelpers:
The only one I've needed thus far in production code is for an explicit value, so maybe we start with only that method and add others if needed. We should check if one or more of these is already used in existing ConfigProvider implementations, and those are good candidates to include as well.
The text was updated successfully, but these errors were encountered:
TestHelpers
contains a bunch of useful methods to easily createFieldResolverStrategy
instances for a single resolution, e.g., for a specific value, or using aSupplier
. Recently I've wanted a few of these in production code. So, create a new utility/factory class that contains methods to easily create instances when you only want a single strategy.It could be named
FieldResolverStrategies
and provide all or only a few of methods that exist inTestHelpers
currently. Here are the signatures fromTestHelpers
:The only one I've needed thus far in production code is for an explicit value, so maybe we start with only that method and add others if needed. We should check if one or more of these is already used in existing
ConfigProvider
implementations, and those are good candidates to include as well.The text was updated successfully, but these errors were encountered: