FLUID-5251: Conditional transformer now only evaluates the relevant block (true/false) #454
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
…sformer, only evaluting the relevant 'input' based on what the condition evaluates to
This was referenced Jan 15, 2014
|
Please resolve this by the method suggested in my JIRA comment - that is, by changing the standard contract of fluid.multiInputTransformFunction, rather than turning the condition transformer into a special case |
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.
Changed condition transformer to a non-standard inputtransformer, only evaluting the relevant 'input' based on what the condition evaluates to