Automapper: union-subtree not propagating through class hierarchy #334
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.
I am converting a project from using ClassMaps to using the AutoMapper in order to simplify the existing project and any future changes. One class inheritance tree in the project is built using UnionSubclassMapping and when attempting to build the NH configuration using the automapper, the following error is thrown:
This inheritance tree has three layers. The AutoMapper was not carrying the knowledge that union-subtree was to be used down to the grandchild object, which caused it to switch and start using joined-subtree, which is not allowed.
I have assembled a patch and a test for checking the issue. I don't know if a similar issue exists for other subclassing strategies. I can also confirm that the patched version of Fluent works with my project and it is now generating correct HBM files.