The objectId was missing from the filter list #1315
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…om the filter list. It was not include because of fix parse-community#1283 about am issue with the userPointers. That should now still be in place since, but I don't 100% understand that issue.
davimacedo
approved these changes
Oct 2, 2019
|
@davimacedo Can we make a release for this bug fix? I'm facing this issue on 2.0.3 which is currently the latest release. |
|
Hi. |
|
I would also appreciate a 2.0.4 for this. |
|
working on this now. should be out shortly. |
beiguancyc
pushed a commit
to beiguancyc/parse-dashboard
that referenced
this pull request
Oct 18, 2019
* parse: (36 commits) prepare for 2.0.4 (parse-community#1347) Only do a complex query for createdAt instead of -createdAt (parse-community#1334) Update parse to the latest version 🚀 (parse-community#1345) Update webpack to the latest version 🚀 (parse-community#1344) Update core-js to the latest version 🚀 (parse-community#1343) Update core-js to the latest version 🚀 (parse-community#1342) Update core-js to the latest version 🚀 (parse-community#1341) Update eslint-plugin-jest to the latest version 🚀 (parse-community#1340) Update eslint-plugin-jest to the latest version 🚀 (parse-community#1339) Update webpack to the latest version 🚀 (parse-community#1338) Update babel7 to the latest version 🚀 (parse-community#1337) Fixed incorrect links to PR details (parse-community#1329) Update babel7 to the latest version 🚀 (parse-community#1335) Update eslint-plugin-react to the latest version 🚀 (parse-community#1327) Update react to the latest version 🚀 (parse-community#1326) Update cross-env to the latest version 🚀 (parse-community#1324) This should resolve parse-community#1297. The objectId was missing from the filter list. (parse-community#1315) Update eslint-plugin-react to the latest version 🚀 (parse-community#1322) Update cross-env to the latest version 🚀 (parse-community#1321) Update eslint-plugin-react to the latest version 🚀 (parse-community#1319) ... # Conflicts: # package-lock.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should resolve #1297. The objectId was missing from the filter list.
It was not include because of fix #1283 about am issue with the userPointers. That should now still be in place since, but I don't 100% understand that issue.