added convenience for adding filters to automaps #29
Conversation
This file contains 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
|
Hey, sorry I haven't got around to merging this in yet. Will hopefully get time soon. |
jagregory
added a commit
that referenced
this pull request
Aug 9, 2011
added convenience for adding filters to automaps
ivaylo5ev
pushed a commit
to ivaylo5ev/fluent-nhibernate
that referenced
this pull request
Sep 26, 2021
added convenience for adding filters to automaps
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.
Combining filters with automapping is a bit awkward. See, for example, this SO question:
http://stackoverflow.com/questions/5728935/property-filter-with-fluent-nhibernate-automapping/6538285
It would be easier to say:
So I added that method. It's pure convenience, so I didn't add a test, but let me know if you think one's needed.