-
Notifications
You must be signed in to change notification settings - Fork 556
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
How to select oneOf value #2528
Labels
Comments
We don't support a such format yet, try with the following schema: "items": {
"type": "object",
"oneOf": [
{
"type": "object",
"properties": {
"mainKey": {
"type": "string",
"description": "Route policy contents as a single quoted string",
"format": "WORD"
}
}
},
{
"type": "object",
"properties": {
"mainKey": {
"type": "null",
"description": "Set value to null to delete this leaf"
}
}
}
]
} |
Thanks for your quick reply. When can we expect this enhancement? |
within 1 or 2 weeks |
aitboudad
added a commit
to aitboudad/ngx-formly
that referenced
this issue
Jan 26, 2022
aitboudad
added a commit
that referenced
this issue
Jan 26, 2022
aitboudad
added a commit
that referenced
this issue
Mar 30, 2022
This issue has been fixed and released as part of v5.12.0 release. Please let us know, in case you are still encountering a similar issue/problem. |
This was referenced Apr 11, 2022
Closed
This was referenced Apr 28, 2022
Closed
This was referenced Jul 19, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://stackblitz.com/edit/angular-vv82f7?file=src%2Fassets%2Fjson-schema%2Fschema_dependencies.json
Check "schema_dependencies" in stackblitz
I want to pick/assign oneOf the values to the mainKey .
Objects inside oneOf can be of any type, hence I cannot assign type : ' object ' to the mainKey
because then it will always give me { mainKey : {} } which cannot be true always,
**since the value can be any string { mainKey : "abc" }, number { mainKey : 123 } , etc **
I guess there should some dynamic behavior for this.
The text was updated successfully, but these errors were encountered: