-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide test checking all components can display the property panel #449
Closed
4 of 5 tasks
Comments
Since we now can use the real component catalog in Jest tests, it's possible to try rendering config form for all the components in the catalog and make sure it doesn't return an error. Would be nice to do the same for all processors/kamelets/languages/dataformats. |
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 2, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (KaotoIO#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (KaotoIO#449)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 2, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (KaotoIO#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (KaotoIO#449) * Added `$comment` to hold the catalog `javaType`, supposed to be used for BeanReferenceField (KaotoIO#470)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 2, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (KaotoIO#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (KaotoIO#449) * Added `$comment` to hold the catalog `javaType`, supposed to be used for BeanReferenceField (KaotoIO#470)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 2, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (KaotoIO#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (KaotoIO#449) * Added `$comment` to hold the catalog `javaType`, supposed to be used for BeanReferenceField (KaotoIO#470)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 2, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (KaotoIO#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (KaotoIO#449) * Added `$comment` to hold the catalog `javaType`, supposed to be used for BeanReferenceField (KaotoIO#470)
lordrip
pushed a commit
that referenced
this issue
Dec 4, 2023
* Moved component-catalog > JSON schema generation to the maven plugin * Fixed array/object related issues in component schema (#448) * Added default value handling for component schema * Added an exhaustive test for rendering component configuration form (#449) * Added `$comment` to hold the catalog `javaType`, supposed to be used for BeanReferenceField (#470)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 5, 2023
* Move kamelet schema generation to the maven plugin * Change `binary` field type to `string` * Add `enum`, `default` and `format` handling * Add exhaustive test for rendering kamelet configuration (KaotoIO#449)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 5, 2023
* Move kamelet schema generation to the maven plugin * Change `binary` field type to `string` * Add `enum`, `default` and `format` handling * Add exhaustive test for rendering kamelet configuration (KaotoIO#449)
lordrip
pushed a commit
that referenced
this issue
Dec 5, 2023
* Move kamelet schema generation to the maven plugin * Change `binary` field type to `string` * Add `enum`, `default` and `format` handling * Add exhaustive test for rendering kamelet configuration (#449)
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 5, 2023
…g form (KaotoIO#449) Also remove warning from uniforms about `additionalProperties` being passed down to the DOM
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 5, 2023
…g form (KaotoIO#449) Also remove warning from uniforms about `additionalProperties` being passed down to the DOM
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 5, 2023
…g form (KaotoIO#449) Also remove warning from uniforms about `additionalProperties` being passed down to the DOM
igarashitm
added a commit
that referenced
this issue
Dec 5, 2023
…g form (#449) (#510) Also remove warning from uniforms about `additionalProperties` being passed down to the DOM Co-authored-by: Lars Heinemann <[email protected]>
This was
linked to
pull requests
Dec 5, 2023
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 7, 2023
* Extract processor JSON schema from main camelYamlDsl.json and put into pattern catalog as a `/propertiesSchema` * Add control comment for complex parameters to `$comment` schema property, such as `class:<class name>`, `expression`, `dataformat`, `loadbalance` for those need special handling for configuration form rendering * Remove oneOf/anyOf structures and extract the one needed for form rendering * Added exhaustive rendering test for all processors Fixes: KaotoIO#448 Fixes: KaotoIO#449
igarashitm
added a commit
that referenced
this issue
Dec 7, 2023
* Extract processor JSON schema from main camelYamlDsl.json and put into pattern catalog as a `/propertiesSchema` * Add control comment for complex parameters to `$comment` schema property, such as `class:<class name>`, `expression`, `dataformat`, `loadbalance` for those need special handling for configuration form rendering * Remove oneOf/anyOf structures and extract the one needed for form rendering * Added exhaustive rendering test for all processors Fixes: #448 Fixes: #449
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the task that needs to be done
At least checking that there is no "Field no found in schema" errors which affected several different components in the past
see:
Tasks
The text was updated successfully, but these errors were encountered: