[Feature] user custom instantiators #243
Open
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.
The idea of this feature is to provide a mechanism for users to define custom instantiators like it exists for custom field value changers. It follows the same idea to let user extends pojo-tester mechanism.
It already exists a mechanism that let the user to select the choosen constructor (explanations here) but it is not efficient when the pojo use provided types from external libraries.
Here are the steps to add pojo tester support for an external librairy types (for example vavr) in an external project :
Instantiator.INSTANCE.attach(VavrTypesInstantiator.class);
Now we can use pojo tester with an object using vavr types, for example :
Detailed example here with vavr collections.