Skip to content

Filters is missing "objectId" in 2.0.3 #1297

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

Closed
omairvaiyani opened this issue Sep 18, 2019 · 2 comments · Fixed by #1315
Closed

Filters is missing "objectId" in 2.0.3 #1297

omairvaiyani opened this issue Sep 18, 2019 · 2 comments · Fixed by #1315

Comments

@omairvaiyani
Copy link

Hey, loving the changes in v2, very happy to see new work happening on this repo! Just a bug I've noticed in 2.0.3, the filters dropdown is missing "objectId". This also happens to be the filter we use most often when searching for a specific record - if others agree, is it also worth having a quick input field, perhaps next to the Class title, which expands an input box and let's us quick find a record by "objectId"?

W0lfw00d added a commit to W0lfw00d/parse-dashboard that referenced this issue Sep 30, 2019
…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.
@W0lfw00d
Copy link
Contributor

It seems to have been becaused by this pull request: #1283

@lukasnagl
Copy link

We’d like to see a quick fix for this. It’s one of the most used filters for us.

davimacedo pushed a commit that referenced this issue Oct 2, 2019
…ist. (#1315)

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.
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this issue 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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants