Repository navigation
10.1 - Add optimal constructor selector - #1028
Merged
Merged
Conversation
…constructor" into a method OptimalConstuctorSelector
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
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.
Changes:
For Record type by default, and other type when using settings
.MapToConstructor(true)a strategy for selecting the optimal constructor will be used.The optimal constructor strategy selects the constructor with the fewest unfilled parameters (i.e., the one with the greatest difference between the number of using sources members and the total number of constructor arguments); in the event of a tie, it favors the most detailed constructor - the one with the highest total number of parameters.