Strip read only fields from serialized beforeSave responses #1964
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
TylerBrock
force-pushed
the
strip-read-only-beforesave
branch
from
f37450d to
830bd55
Compare
TylerBrock
force-pushed
the
strip-read-only-beforesave
branch
from
830bd55 to
f212f33
Compare
TylerBrock
force-pushed
the
strip-read-only-beforesave
branch
from
f212f33 to
86f2808
Compare
Current coverage is 91.90%
@@ master #1964 diff @@
==========================================
Files 91 91
Lines 6397 6399 +2
Methods 1094 1094
Messages 0 0
Branches 1342 1342
==========================================
+ Hits 5875 5881 +6
+ Misses 522 518 -4
Partials 0 0
|
|
@TylerBrock updated the pull request. |
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.
This fixes #1949 and makes parse-server behave like api.parse.com with regards to how response objects for beforeSave hooks are handled.