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
We are having an issues with the != operator. When we try to query where _id!=64514704b973cc48c724d563 instead of resolving this as $ne it instead is turning into $not which happens at this line
The reason this triggers is becasue we have a caster for this field:
What I would like to know is when is the $not operator intended to be added? In the documentation and examples I only see it next to regex values. Are there other cases where $not should be added as well, or would it be safe to also check value instanceof RegExp before using that condition?
The text was updated successfully, but these errors were encountered:
We are having an issues with the
!=
operator. When we try to query where_id!=64514704b973cc48c724d563
instead of resolving this as$ne
it instead is turning into$not
which happens at this lineThe reason this triggers is becasue we have a caster for this field:
What I would like to know is when is the
$not
operator intended to be added? In the documentation and examples I only see it next to regex values. Are there other cases where$not
should be added as well, or would it be safe to also checkvalue instanceof RegExp
before using that condition?The text was updated successfully, but these errors were encountered: