Skip to content
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

Wrong CLP shown after creating new class #1784

Closed
4 tasks done
sadakchap opened this issue Sep 6, 2021 · 3 comments
Closed
4 tasks done

Wrong CLP shown after creating new class #1784

sadakchap opened this issue Sep 6, 2021 · 3 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@sadakchap
Copy link
Member

New Issue Checklist

Issue Description

Wrong CLP info is shown after creating new class for first time, Until reload. Classes are created with Public read & write enabled by default. But, after creating a new class dashboard is showing Protected CLP for that class.

Steps to reproduce

CLPBug.mp4

Actual Outcome

Showing wrong CLP for new class. i.e., showing Protected CLP for new class which was created with Public Read & write Enabled CLP.

Expected Outcome

Should show correct CLP for the newly created class as well.

Environment

Dashboard

  • Parse Dashboard version: 2.2.0
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Chrome
  • Browser version: Version 92.0.4515.159

Server

  • Parse Server version: 4.10.3
  • Operating system: Ubuntu
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): remote

Database

  • System (MongoDB or Postgres): mongoDB
  • Database version: 3.6
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): remote

Logs

@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@sadakchap sadakchap added the type:bug Impaired feature or lacking behavior that is likely assumed label Sep 6, 2021
@sadakchap
Copy link
Member Author

Here's the pr

@mtrezza
Copy link
Member

mtrezza commented Sep 7, 2021

Closed via #1785

@mtrezza mtrezza closed this as completed Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants