-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix select exclude queries #7242
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7242 +/- ##
=======================================
Coverage 93.90% 93.90%
=======================================
Files 181 181
Lines 13210 13228 +18
=======================================
+ Hits 12405 12422 +17
- Misses 805 806 +1
Continue to review full report at Codecov.
|
Thanks for the PR. I think we would do good to I think we have to be careful in removing or changing a test case. I actually just fixed a Parse Server issue for |
I think codecov is reporting in the PR incorrectly, when you look at the full report there's actually a slight increase instead of decrease https://app.codecov.io/gh/parse-community/parse-server/compare/7242 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just want to mention that there is an ongoing discussion about this change in the issue. So that this doesn't get merged by mistake before we come to a conclusion.
Supports changes made in pending [PR](parse-community/parse-server#7242). Can see [here](parse-community/parse-server#7245) for further discussion.
@cbaker6 sorry for the late reply. I’ll review this in detail this weekend |
@dplewis let me know if any additional questions come up regarding this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cbaker6 Sorry for the late reply and thank you for this PR. I have a few comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
🎉 This change has been released in version 5.0.0-beta.1 |
🎉 This change has been released in version 5.0.0 |
New Pull Request Checklist
Issue Description
Related issue: to an issue discovered and Fixes #7245 and on the Parse-Swift SDK, parse-community/Parse-Swift#88
The keys and excludeKeys on the server are not digesting actual JSON arrays, ["yolo", ...], but instead digesting "yolo", .... Somehow JS treats both of these the same (I say this because the fixed PR I have for the server works with just removing 1 test case, more on this in the PR), but the server doesn't like it the way the Swift JSON encoder sends it, ["yolo", ...]. Note that this is the JSON encoder straight from Apples Swift source code and not the custom one used here for ParseObjects, so if it was encoding arrays incorrectly I'm sure it would have been caught awhile ago.
This PR has the possibility of being breaking change for some users due to:Approach
Make
keys
andexcludeKeys
use the same strategy as a similar property likeinclude
which takes array of strings also,parse-server/src/Routers/ClassesRouter.js
Lines 60 to 68 in b4920a6
TODOs before merging