Move entity mapping for void, object and duck to a virtual method #81
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
bamboo
added a commit
that referenced
this pull request
Dec 16, 2013
Move entity mapping for void, object and duck to a virtual method
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.
In BooJs I want to map
System.Objectto a custom type. SinceReflectionTypeSystemProvidermapsobject,duckandvoidin its constructor is not possible to apply a custom mapping for them in descendant implementations because theMemoizedFunctioncache complain that the key is already defined.This patch moves the mapping to a virtual
Initializemethod that can be overridden in order to configure custom mappings for any type.