fix: Expressions not starting with "=" can resolve to a regular TextField #4507
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.
Description
resolveFieldWidget assumed that all expressions start with "=". But there are two types of expressions:
As such, schema types that were oneOf between expression (not equalsExpression) and a list of non string types were enable to resolve when the input was a string. Such an example is condition:
This PR addresses this issue by resolving to a regular input field when the type is an expression.
Task Item
fixes #4479
Screenshots