fix: anyof condition breaking UI #221
Merged
Conversation
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
antoniocapelo
requested review from
dragidavid,
eng-almeida,
lukad and
sandrina-p
eng-almeida
previously approved these changes
Jul 23, 2025
lukad
approved these changes
Jul 24, 2025
antoniocapelo
deleted the
devxp-3292-fix-anyof-condition-for-json-schema-form-v1
branch
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.
The current
anyOfimplementation has 2 issues:visually it breaks the form, as it wrongly interprets root anyOf as if it belonged to a select or checkbox group options
the error message is a string with a stringified json object which is wrong. It should target individual fields with issues, and not treat the anyOf as a single error.
This MR addresses it by:
optionsif the field is the rootanyOfis not valid