-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add BeanReferenceField #470
Labels
Milestone
Comments
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)
|
Mock up - plumbing is not completed yet, but showing the basic workflow output.mp4 |
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 12, 2023
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 12, 2023
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 12, 2023
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Dec 13, 2023
`uniforms` connected fields require two things: 1. A componentDetectorContext provider 2. AutoForm parent which hold the schema This commit adds both items to make the skipped test work relates: KaotoIO#470
igarashitm
pushed a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
`uniforms` connected fields require two things: 1. A componentDetectorContext provider 2. AutoForm parent which hold the schema This commit adds both items to make the skipped test work relates: KaotoIO#470
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
Otherwise it fails to add a bean if there's no existing `beans`
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
igarashitm
pushed a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
`uniforms` connected fields require two things: 1. A componentDetectorContext provider 2. AutoForm parent which hold the schema This commit adds both items to make the skipped test work relates: KaotoIO#470
igarashitm
added a commit
to igarashitm/kaoto
that referenced
this issue
Dec 13, 2023
Otherwise it fails to add a bean if there's no existing `beans`
lordrip
pushed a commit
that referenced
this issue
Dec 13, 2023
lordrip
added a commit
that referenced
this issue
Dec 13, 2023
`uniforms` connected fields require two things: 1. A componentDetectorContext provider 2. AutoForm parent which hold the schema This commit adds both items to make the skipped test work relates: #470
lordrip
pushed a commit
that referenced
this issue
Dec 13, 2023
Otherwise it fails to add a bean if there's no existing `beans`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Please describe the feature that you want to propose
cf. #245
Currently all the
object
type parameter is showingPropertiesField
, for exampleDataSource
parameter ofSQL
step looks like thisBut the component catalog has
"javaType": "javax.sql.DataSource"
, which indicates this is a specific type of Java object, and I believe in this case the parameter should have a reference to a bean with#
prefix.Introduce BeanReferenceField for step configuration form which allows both
For the parameters which
object
typeenum
javaType
other thanjava.lang.Object
java.lang.Object
parameter should be handled with BeanReferenceFiend instead of PropertiesFieldWe might be able to useformat
keyword in JSON schema to indicate to useBeanReferenceField
from schema side.https://json-schema.org/draft/2020-12/json-schema-validation#name-vocabularies-for-semantic-cUnfortunately not. Uniforms throws an error if it cannot understand
format
(#505)Instead we're currently using
$comment
for attaching additional metadata to the properties JSON schema.The text was updated successfully, but these errors were encountered: