can now map to interface #57
Open
Conversation
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
robert-bor
force-pushed
the
master
branch
12 times, most recently
from
3787c8f to
87a3d88
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This feature does introduce a (provided) dependency between the bean mapper core and spring. I know that this goes against the initial design goal.
A possible solution would be to rename beanmapper-spring to beanmapper-mvc as this library primarly consists of mvc logic anyway. Also the core should dynamically check if spring is on the classpath, rather than throwing class not found exceptions.
By calling the map from an object to an interface type you create a 'projection' of the source object. This proxy stays in synch with the actual source object, providing real time data. See the issue for more details.