fix(gatsby): Fix Loki query operators special casing #11517
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are subtle differences between Loki and Sift query operators that we are trying to account for. This fixes some of those:
$eq
and$ne
, which translates to$contains
and$containsNone
in Loki$nin
addedfalse
, which should beundefined
. This also needed removing cloning the query args with JSON.parse/stringify, because undefined=>null, but it does not seem to serve a purpose anymore anyway.{ $ne: true }
now handles nesting levels > 2, e.g.{ "foo.bar.baz": { $ne: true } }
{ "": {} }
for an empty object.