Add preventSchemaEdits option to apps and hide or disable buttons to manipulate classes and columns #960
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.
In a project using Parse Dashboard as a middleware of a Parse Server, I want to disable the actions modifying the schema.
I know there is way to fail these actions when using the
readOnlyMasterKey
, but I need to let my user add / edit / delete rows, I just want them to not change the schema. The best way I found so far is to hide the buttons:To support that, I added a new
preventSchemaEdits
option to apps, defaulted tofalse
.Eg:
Any feedback welcome.