-
Notifications
You must be signed in to change notification settings - Fork 99
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
Breaking change to functionality in version 8 #152
Comments
Bummer! If this is intentional, I may need to fork v7 and start maintaining this fork. |
I'm also facing this issue. I think there was some misinterpretation in #117 which has caused this issue. Whatever the case, for me, explicitly using This functionality is now even more different from mongo. |
Sorry everyone, this issue should be fixed now in
You're right, this was a misinterpretation 🙈. Object exactness should have only been applied to properties of the top-most query. |
I'll check out |
8.3.2 resolved most issues we're facing, but there seem to be some leftovers
returns true on sift 7, but false on sift 8.3.2 |
Just pushed fixes to |
Thanks, Craig. Do you have these cases under test coverage?
…On Tue, Apr 30, 2019 at 6:22 AM Craig Condon ***@***.***> wrote:
there seem to be some leftovers
Just pushed fixes to 8.3.3, let me know if it works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAZY6KVOPSTMVXOTDC66ICDPTBB2LANCNFSM4HI5SVGQ>
.
|
seems like the latest update fixed all tests in our not that huge test suite 👍! |
|
@redgeoff is the issue fixed for you? If so I'll go ahead and close this ticket. |
Thanks, I’ll try and test this tonight
…On Tue, Apr 30, 2019 at 6:52 AM Craig Condon ***@***.***> wrote:
@redgeoff <https://github.com/redgeoff> is the issue fixed for you? If so
I'll go ahead and close this ticket.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAZY6KVGPWBHUNRKI34SBSTPTBFLNANCNFSM4HI5SVGQ>
.
|
I can confirm that after reverting my changes and upgrading to |
v8.3.3 appears to have fixed the problem. Thanks @crcn! |
I want to start off by saying that sift rocks and it has been super helpful in mson!
Unfortunately, I recently tried to upgrade from v7 to v8 and there appears to be a massive breaking change, i.e. you now need to specify all the attributes in the query before anything is matched.
Take the example:
with sift v7.0.1 and earlier, you get the output of
[ { foo: 'bar', yar: 'nar' } ]
, but with v8.0.1 and later, you get[]
To get an output of
[ { foo: 'bar', yar: 'nar' } ]
with v8.0.1, you need to include all the properties, e.g.Is this intentional or is this a bug?
The text was updated successfully, but these errors were encountered: