FIO-10822: fixed an issue where evaluations donot work if returned variable is in middle of the custom logic or is not 'value'#20
Merged
brendanbond merged 1 commit intomasterfrom Nov 6, 2025
Conversation
…riable is in middle of the custom logic or is not 'value'
brendanbond
approved these changes
Nov 6, 2025
This file contains hidden or 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
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.
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-10822
Description
What changed?
Fixed evaluations for use case when expected returned value is not 'value' but 'valid' or some other + fixed issue where returned value is not in the first line of custom logic.
How has this PR been tested?
Manually
Checklist: