`patternProperties` number keys make the input get rendered at the very top of the `Form` · rjsf-team/react-jsonschema-form#4631

(7 comments) (0 reactions) (0 assignees)TypeScript (13,175 stars) (2,136 forks)batch import

bugcorehelp wanted

説明

Prerequisites

I have searched the existing issues
I understand that providing a SSCCE example is tremendously useful to the maintainers.
I have read the documentation
Ideally, I'm providing a sample JSFiddle, Codesandbox.io or preferably a shared playground link demonstrating the issue.

What theme are you using?

core

Version

6.0.0-beta.8

Current Behavior

Adding a new patternProperties key that is a number makes the key name input get rendered at the very top of the Form:

Notice that keys that have non-numeric characters in them are not affected by this issue.

Expected Behavior

Keys should at least remain grouped. It would be intuitive to always have them rendered in the order they were added.

If they should be reordered dynamically amongst themselves, I don't know. Maybe this could be a customizable behaviour set through a new prop or UiSchema property? Just like lists allow reordering, maybe?

Steps To Reproduce

Go to the playground patternProperties example.
Change the regex of the JSON Schema patternproperties property to "(.*?)", so it matches anything.
Add a new property with a purely numeric key.
Observe where the field gets rendered.

Environment

Irrelevant

Anything else?

No response

コントリビューターガイド

技術スタック: typescriptreactjavascript
領域: frontend
Issue 種別: bug
難度: 3
推定時間: 1-2 days
活動状況: fresh
明確さ: clear
前提条件: Knowledge of ReactUnderstanding of JSON SchemaFamiliarity with react jsonschema form internals
初心者向け度: 55
調査方針: The bug occurs when patternProperties keys that are purely numeric cause the input field to render at the top of the form instead of in the correct section. The issue likely lies in the component that handles patternProperties rendering, possibly in the way keys are sorted or grouped. Review the patternProperties implementation, particularly how keys are validated as strings versus numbers and how they are ordered when added. Look at the playground example and the code in the 'Utils' or 'Form' component related to patternProperties. Check if there is any numeric key sorting that overrides the insertion order. The maintainers might need to ensure that numeric keys are treated as strings and that the order of addition is preserved.