📙
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Open the Cloud Code guide at the beforeFind section and review the linked Parse Server security guidance. Remove the recommendation that triggers should prevent data access, then add an explicit warning linking to the security guide. Done means the unsafe access-control advice is gone and readers are directed to the dedicated security mechanisms.
Written by the indexing model from the issue text.
Description
Link to section:
In some cases you may want to transform an incoming query, adding an additional limit or increasing the default limit, adding extra includes or restrict the results to a subset of keys. You can do so with the beforeFind trigger.
https://docs.parseplatform.org/cloudcode/guide/#beforefind
What is the issue?
Triggers are suggested to be used to prevent access to data. This should not be recommended as Parse Server provides a dedicated security layer for access restrictions. The docs as they are now encourage unsafe, custom practices for access control instead of using the more elaborate mechanisms of access control that were built for that purpose.
Here is just 1 example: https://stackoverflow.com/questions/73575340/parse-platform-authenticate-a-query-in-a-beforefind-trigger
Can you propose a solution?
Coment should be removed and instead an explicitly warning note should be added to triggers with a link to https://docs.parseplatform.org/parse-server/guide/#security.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 506
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from parse-community/docs
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
parse-community/docs#889 · 7 comments ·
-
docs:sdk-js
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
parse-community/docs#961 ·
-
type:bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
parse-community/docs#950 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
parse-community/docs#947 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
parse-community/docs#929 ·
All issues in parse-community/docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100