Admin Generator (Future): Add FinalFormRangeInput
to form generator
#2612
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
FinalFormRangeInput
fields can now be generated in forms. The new field type isnumberRange
. Data of the field is saved in this format:{ min: number, max: number }
The names
min
andmax
are currently hardcoded, as they have to be named this way.FinalFormRangeInput
passes the values named like this.Example
The field with all possible options:
The field in product.entity:
Example in demo: #2593
Screenshots/screencasts
Creating a Product with a price range:
Screen.Recording.2024-10-08.at.11.52.42.mp4
Example of editing a price range:
Screen.Recording.2024-10-08.at.11.54.01.mp4
Changeset
Related tasks and documents
Jira Task: https://vivid-planet.atlassian.net/browse/SVK-124
Open TODOs/questions
Further information