feat: Allow Parse.Object field names to begin with underscore _ to access internal fields of Parse Server
#2475
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
Thanks for opening this pull request! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #2475 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 64 64
Lines 6256 6256
Branches 1451 1447 -4
=========================================
Hits 6256 6256 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
mtrezza
previously approved these changes
Mar 5, 2025
mtrezza
changed the title
Parse.Object field names to start with underscore to access internal fields of Parse Server
mtrezza
changed the title
Parse.Object field names to start with underscore to access internal fields of Parse ServerParse.Object field names to begin with underscore to access internal fields of Parse Server
mtrezza
changed the title
Parse.Object field names to begin with underscore to access internal fields of Parse ServerParse.Object field names to begin with underscore _ to access internal fields of Parse Server
|
Does this also remove the restriction for queries, for example |
|
The restriction for queries must be handled server side |
|
So does the Parse JS SDK already allow sending a query with |
|
Oh yes you can send the query |
mtrezza
approved these changes
Mar 5, 2025
parseplatformorg
pushed a commit
that referenced
this pull request
Mar 5, 2025
# [6.1.0-alpha.1](6.0.0...6.1.0-alpha.1) (2025-03-05) ### Features * Allow `Parse.Object` field names to begin with underscore `_` to access internal fields of Parse Server ([#2475](#2475)) ([08e43ba](08e43ba))
|
🎉 This change has been released in version 6.1.0-alpha.1 |
parseplatformorg
pushed a commit
that referenced
this pull request
Mar 17, 2025
# [6.1.0](6.0.0...6.1.0) (2025-03-17) ### Features * Add `Parse.Query` option `useMaintenanceKey` ([#2484](#2484)) ([2ead3f3](2ead3f3)) * Allow `Parse.Object` field names to begin with underscore `_` to access internal fields of Parse Server ([#2475](#2475)) ([08e43ba](08e43ba)) * Publish TypeScript definitions ([#2491](#2491)) ([fc3e573](fc3e573))
|
🎉 This change has been released in version 6.1.0 |
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.
Pull Request
Issue
With the introduction of access scopes, internal fields can be read from and written to.
Closes: #2474
Approach
Tasks