-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
According to the JSON schema spec, the default keyword specifies a default value that should only be used for informational purposes on the client side. Pre-filling a form with schema default values is not semantically correct and can result in invalid form inputs since default values are not required to validate against the schema.
Per the JSON Schema spec:
The default keyword specifies a default value. This value is not used to fill in missing values during the validation process. Non-validation tools such as documentation generators or form generators may use this value to give hints to users about how to use a value. However, default is typically used to express that if a value is missing, then the value is semantically the same as if the value was present with the default value. The value of default should validate against the schema in which it resides, but that isn’t required.
AC:
- Form fields generated from JSON schema are not pre-filled with values defined by the "default" keyword.
- blocks
-
KATA-1372 UI: switching between the form and yaml views when installing kataconfig shows different values
- Closed
- incorporates
-
OCPBUGS-3952 The form view fills up properties of schema from children default values even if no defaults are specified for parent schema
- Closed
- is blocked by
-
CONSOLE-3637 Update rjsf to latest
- To Do