#10 allow custom implementation names#27
Merged
filiphr merged 2 commits intoMay 31, 2026
Conversation
hduelme
force-pushed
the
allow-custom-implementation-names
branch
from
d729700 to
d54d070
Compare
filiphr
requested changes
May 31, 2026
hduelme
force-pushed
the
allow-custom-implementation-names
branch
from
562a3d2 to
1aaf647
Compare
Contributor
Author
|
@filiphr thanks for the fast review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #10 by allowing custom implementation names.
The implementation is inspired by
@Mapperfrom MapStruct.