Skip to content

Fix CLP dialog for pointer fields #1283

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

Merged
merged 2 commits into from
Sep 13, 2019

Conversation

davimacedo
Copy link
Member

close #1280

@douglasmuraoka douglasmuraoka merged commit 8b9d647 into parse-community:master Sep 13, 2019
@douglasmuraoka douglasmuraoka deleted the fix1280 branch September 13, 2019 14:23
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this pull request Sep 18, 2019
* parse:
  Release v2.0.3 (parse-community#1294)
  Update cross-env to the latest version 🚀 (parse-community#1295)
  Fix: Force pointer array items to always be pointers (parse-community#1291)
  Update webpack-cli to the latest version 🚀 (parse-community#1292)
  Update graphql to the latest version 🚀 (parse-community#1290)
  Update eslint to the latest version 🚀 (parse-community#1289)
  Update graphql to the latest version 🚀 (parse-community#1288)
  Update webpack to the latest version 🚀 (parse-community#1287)
  Fix CLP dialog for pointer fields (parse-community#1283)
  Update puppeteer to the latest version 🚀 (parse-community#1286)
  Update webpack to the latest version 🚀 (parse-community#1285)
  Update history to the latest version 🚀 (parse-community#1284)
  Fix: Feature "masterkey parameters" requires Parse Server >= 3.9.0 (parse-community#1281)
  Update webpack to the latest version 🚀 (parse-community#1282)
  Update history to the latest version 🚀 (parse-community#1279)

# Conflicts:
#	package-lock.json
W0lfw00d added a commit to W0lfw00d/parse-dashboard that referenced this pull request 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.
davimacedo pushed a commit that referenced this pull request 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.
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 this pull request may close these issues.

Can not use pointer permission on class.
2 participants