-
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
Support nested anyOf/oneOf schemas #948
Comments
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 15, 2024
Extract single OneOf definition from AnyOf definition and put it into the root definitions. relates: KaotoIO#948 relates: KaotoIO#560
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 18, 2024
Currently, in case a schema contains a `oneOf` array, `uniforms` combines all `oneOf` definitions in a single schema definition. The issue with this approach is that combine potentially non-compatible schemas, like the `errorHandler` one, since we need to specify a single property. This commit extends the `getField` method from the uniforms `JSONSchemaBridge` to add the `oneOf` definitions into the field, this way, we could use this information in the form to render an UI control to select a given schema relates: KaotoIO#948 relates: KaotoIO#560
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 18, 2024
Currently, in case a schema contains a `oneOf` array, `uniforms` combines all `oneOf` definitions in a single schema definition. The issue with this approach is that combine potentially non-compatible schemas, like the `errorHandler` one, since we need to specify a single property. This commit extends the `getField` method from the uniforms `JSONSchemaBridge` to add the `oneOf` definitions into the field, this way, we could use this information in the form to render an UI control to select a given schema relates: KaotoIO#948 relates: KaotoIO#560
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 18, 2024
Currently, in case a schema contains a `oneOf` array, `uniforms` combines all `oneOf` definitions in a single schema definition. The issue with this approach is that combine potentially non-compatible schemas, like the `errorHandler` one, since we need to specify a single property. This commit extends the `getField` method from the uniforms `JSONSchemaBridge` to add the `oneOf` definitions into the field, this way, we could use this information in the form to render an UI control to select a given schema relates: KaotoIO#948 relates: KaotoIO#560
lordrip
added a commit
that referenced
this issue
Mar 18, 2024
Currently, in case a schema contains a `oneOf` array, `uniforms` combines all `oneOf` definitions in a single schema definition. The issue with this approach is that combine potentially non-compatible schemas, like the `errorHandler` one, since we need to specify a single property. This commit extends the `getField` method from the uniforms `JSONSchemaBridge` to add the `oneOf` definitions into the field, this way, we could use this information in the form to render an UI control to select a given schema relates: #948 relates: #560
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 19, 2024
Currently, there's partial support for `oneOf` in the `uniforms` library. This commit adds a new `OneOfField` component that shows a selector to pick which schema should the form generate. Also, if a model is already defined, the closest schema is selected automatically. fix: KaotoIO#560 relates: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 19, 2024
Currently, there's partial support for `oneOf` in the `uniforms` library. This commit adds a new `OneOfField` component that shows a selector to pick which schema should the form generate. Also, if a model is already defined, the closest schema is selected automatically. fix: KaotoIO#560 relates: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 19, 2024
Currently, there's partial support for `oneOf` in the `uniforms` library. This commit adds a new `OneOfField` component that shows a selector to pick which schema should the form generate. Also, if a model is already defined, the closest schema is selected automatically. fix: KaotoIO#560 relates: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 20, 2024
Currently, there's partial support for `oneOf` in the `uniforms` library. This commit adds a new `OneOfField` component that shows a selector to pick which schema should the form generate. Also, if a model is already defined, the closest schema is selected automatically. fix: KaotoIO#560 relates: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 20, 2024
Currently, there's partial support for `oneOf` in the `uniforms` library. This commit adds a new `OneOfField` component that shows a selector to pick which schema should the form generate. Also, if a model is already defined, the closest schema is selected automatically. fix: KaotoIO#560 relates: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Oct 9, 2024
Currently, we have partial support for the `oneOf` schemas. This commit cleans up the generated schemas, by removing the `not` definition from `oneOf` and also removing the empty properties like: ''' { property: { } } ''' fix: KaotoIO#1550 fix: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Oct 9, 2024
Currently, we have partial support for the `oneOf` schemas. This commit cleans up the generated schemas, by removing the `not` definition from `oneOf` and also removing the empty properties like: ''' { property: { } } ''' fix: KaotoIO#1550 fix: KaotoIO#948
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Oct 10, 2024
Currently, we have partial support for the `oneOf` schemas. This commit cleans up the generated schemas, by removing the `not` definition from `oneOf` and also removing the empty properties like: ''' { property: { } } ''' fix: KaotoIO#1550 fix: KaotoIO#948
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the feature that you want to propose
Currently, there's partial support for
anyOf/oneOf
definitions. It's necessary to support multiple levels of nesting of those definitions, for instance, theerrorHandler
definition contains oneanyOf
with subsequent nestedoneOf
The text was updated successfully, but these errors were encountered: