This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
fix(steps-details): Required object type's parameters are lost #1605
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
Currently, having a step with a required object type parameter gets removed from the Code Editor upon opening the step's details panel.
This issue occurs because we're instructing
uniforms
that we have a required object property without a default or initial value.Once
uniforms
tries to build the initial form value, it returns an empty object. This happens here.Changes
Considering that there are no current plans to support object property definitions, the workaround is to provide a default value alongside the schema to feed the initial value of object properties.
Before
Screencast.from.2023-03-31.13-11-26.webm
After
Screencast.from.2023-03-31.13-10-26.webm
Fixes: #1603