feat: handle interface constructor registration #514
Merged
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.
By default, the mapper cannot instantiate an interface, as it does not
know which implementation to use. To do so, the
MapperBuilder::infer()
method can be used, but it is cumbersome in most cases.
It is now also possible to register a constructor for an interface, in
the same way as for a class.
Because the mapper cannot automatically guess which implementation can
be used for an interface, it is not possible to use the
Constructor
attribute, the
MapperBuilder::registerConstructor()
method must beused instead.
In the example below, the mapper is taught how to instantiate an
implementation of
UuidInterface
from packageramsey/uuid
:Fixes #217
Fixes #426