Add ability to compile all mappings and then throw AggregateException#363
Merged
andrerav merged 1 commit intoMapsterMapper:masterfrom Feb 20, 2022
Merged
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
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.
Hi, guys. We would like to have ability try to compile all mapping configurations in solution and only then fail if something is wrong. We are going to add call Compile method in startup time. Currently, I see only first incorrect mapping configuration and I have to start my solution each time to discover only 1 problem. With this change, I just need to start up my project only one time to get all mapping errors.
@chaowlert