You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
JSON Schema $or querySyntax should allow additional properties #3550
A common use-case would be I have a complex nested object in my schema and I want to run an $or query for 'some.nested.path': true
In order to do this I have to list 'some.nested.path' separately in my querySchema. I think for paths containing types like ObjectIds this makes sense because there is a data transformation taking place. However, for simple types like a boolean, string, number, etc. the query would run just fine if I simply changed my querySchema to additionalProperties: true.
Suggestion to make $or, $and, etc allow additional properties optionally as well.
When I query 'account.name' outside of the $or it works fine, no error.
Also using it inside the $or but commenting out the query validation hook also works.
For me setting additionalProperties: true makes no difference, I still get the same error.
So it's just a validation issue, it all works as expected.
Can you provide an example of how you specified the relational query syntax?
Activity
EmileSpecs commentedon Nov 14, 2024
Hi @ha6755ad
Do I understand correctly though that you have gotten this to work?
I can't get it to work, I get the error: "message: 'must NOT have additional properties'"
I'm trying to query:
And my querySchema is defined:
When I query
'account.name'outside of the$orit works fine, no error.Also using it inside the
$orbut commenting out the query validation hook also works.For me setting
additionalProperties: truemakes no difference, I still get the same error.So it's just a validation issue, it all works as expected.
Can you provide an example of how you specified the relational query syntax?
Thanks!