Feature: Add new prop duplicateKeySuffixSeparator for additionalProperties #3048
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.
Reasons for making this change
This was originally done in #2467, porting to v5 here.
When using
additionalProperties
and a duplicate property key is added, RJSF automatically changes the duplicate key from e.g.collision
tocollision-1
.I have a use case where we use
additionalProperties
, but-
is an illegal character for our property keys. I added a FormPropduplicateKeySuffixSeparator
to override-
with any string.Couple of questions
uiSchema
to change the separator per object field. I do not need this for my use case, but it's a potential change that could be made.Checklist
npm run test:update
to update snapshots, if needed.