parse-community / parse-community/parse-server
Role-pointer column in CLP
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Would it be possible to implement Role-pointer CLP permission?
Currently we can add a User-pointer column to CLP, but Role-pointer CLP is not allowed.
EXAMPLE:
In my CLP, I need to disable public Find, enable public Get and enable Find for certain Role. But each row has different Role that it should be visible for. It would be solved with a Role-pointer column CLP, but CLP does not allow me to add Role-pointer column.
It seems to my that it might be easy to implement, since Role CLP is possible (just allowing the pointer..). Unfortunately I can't do it by myself, my skills in js are not that good.
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 tracing Parse Server's CLP handling for User-pointer permissions and the existing Role CLP path. Review the related permission tests, then define coverage for a Role-pointer column where each object may reference a different role. Done means the CLP accepts that pointer and enforces Find and Get access as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100