rjsf-team/react-jsonschema-form

Problem with contains condition in the array field and conditionally rendered subschema with the integer keys when liveOmmit and omitExtraData are set to true

Open

#3,920 opened on Oct 25, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (2,136 forks)batch import
any-one-all-ofarraysbughelp wantedif-then-else

Repository metrics

Stars
 (13,175 stars)
PR merge metrics
 (Avg merge 3d 17h) (32 merged PRs in 30d)

Description

Prerequisites

What theme are you using?

mui

Version

5.13.2

Current Behavior

I have hit a strange bug, not sure where to look, so I will post working and not working schemas. Hopefully, the maintainers will have an idea of what is wrong.

#1. if-then with contains. The conditionally rendered schema has string keys. This works. #2. if-then with contains. The conditionally rendered schema has integer keys. This does not work.

Both work well when liveOmmit and omitExtraData are set to false

Expected Behavior

I would expect that both scenarios work with turned on liveOmmit and omitExtraData. However it seems that they reset the field that is used for rendering the dependent schema, but only if that field options match the keys in the dependent schema. This looks like a bug to me

Steps To Reproduce

#1

#2

Environment

- OS: MacOsx
- Node: latest
- npm: latest

Anything else?

No response

Contributor guide

Research direction
Investigate the logic for `liveOmit` and `omitExtraData` when processing conditional schemas with integer keys. Focus on the `if then` handling and the `contains` condition. Check how the form state resets properties when the keys match integer values.
Tech stack
typescriptreactjavascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40