-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
type:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
type:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed