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.