Remove security editor from browser #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
drew-gross
force-pushed
the
remove-security-editor
branch
from
6ef0de9 to
b880821
Compare
drew-gross
added a commit
that referenced
this pull request
Feb 29, 2016
Remove security editor from browser
douglasmuraoka
pushed a commit
that referenced
this pull request
Nov 29, 2019
Changes the label to email warning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think we would want this to be part of the
schemaspart of theenabledFeaturesobject, but there is also CLPs vs Pointer Permissions so it's not as simple as the other cases. So punt on it for now, we can change this when we actually go to add stuff to the Parse Server schemas API.