Skip to content

RegisterCustom should come before ComplexMapCondition#118

Open
high1 wants to merge 1 commit intofluentsprings:masterfrom
high1:master
Open

RegisterCustom should come before ComplexMapCondition#118
high1 wants to merge 1 commit intofluentsprings:masterfrom
high1:master

Conversation

@high1
Copy link

@high1 high1 commented Oct 14, 2016

  • RegisterCustom was used only if ComplexMapCondition was true, it should
    always be used regardless of the map condition complexity, so it was moved
    before
  • removed checkNullExp - registration should take care of the null values itself

- RegisterCustom was used only if ComplexMapCondition was true, it should
  always be used regardless of the map condition complexity, so it was moved
  before
- removed checkNullExp - registration should take care of the null values itself
@high1
Copy link
Author

high1 commented Oct 14, 2016

This should solve issues with RegisterCustom - it was not always used, and not it will be. I removed checkNullExp, because I think that if a user does register a custom mapping, it should take care of possible null values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments