parse-community / parse-community/parse-server
Enhancements for protectedFields in Create/Update Operations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Description:
This is a follow-up to the closed issue #6458 regarding the limitations and handling of protectedFields in Parse Server.
Current Behavior:
protectedFields hides fields during get/find but allows create/update to modify them.
Users can currently add constraints using protected fields in queries, which may bypass protection unintentionally.
Proposals:
Introduce a stricter error-throwing mechanism when protected fields are involved in mutations.
Provide a way to enforce constraints dynamically based on pointer fields in queries.
Link to original issue: #6458
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #6458 and tracing the current protectedFields behavior for get/find, create, and update operations. Clarify how mutations involving protected fields should fail and how pointer-based query constraints should be enforced. Done requires an agreed scope and corresponding tests for both proposed behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100