-
Notifications
You must be signed in to change notification settings - Fork 16
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
Allow passing of empty JSON Object ({ }
) for sort
for find
and findOne
Commands
#572
Comments
@jeffreyscarpenter suggested we might want to error out instead; noting for now. Will start by first adding a test to see what happens currently; can decide on right action to take later today. |
{ }
) for sort
for find
Command{ }
) for sort
for findOne
Command
Odd: neither |
…for `sort` for `find()`/`findOne()`
I am copying the code blocks that make for a reproducible example. In my experience, setup
working
faulty
all-working
|
…for `sort` for `find()`/`findOne()`
Thank you @hemidactylus -- that should allow reproduction; either with empty filter or empty options or perhaps both. Or could be filter on non-doc-id field too. |
{ }
) for sort
for findOne
Command{ }
) for sort
for find
and findOne
Commands
Ok can reproduce and have a simple fix I think, see #576 . |
(reported by user)
Looks like passing an "empty"
sort
argument (as opposed to passing nothing, ornull
) tofind
and/orfindOne
Command leads to an exception. It should instead be handled same as missing/null value.The text was updated successfully, but these errors were encountered: