Fix to allow for providing double value constants in both inline and WOD bindings when OGNL enabled #780
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
…d WOD bindings (e.g. value="$1.5" or value = 1.5) instead of passing in Strings, which then need to be converted (mimics standard WO behavior without OGNL enabled)
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.
Fix to allow for providing double value constants in both inline and WOD bindings (e.g. value="$1.5" or value = 1.5) when OGNL is enabled. Currently, in order to pass in a double value you have to pass in a string and then convert it to a double in your code. If you try to pass in a double, an exception is thrown. This fix mimics the functionality in a stock WO app without Wonder and OGNL.