fix permissions when you are not the owner of a /resource-based link
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
This requires searching back to resources that you do have permissions to, respecting read vs write vs owner
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.
Research direction
Start by locating the /resource-based link permission-resolution entry point and trace how the server searches for accessible resources. Verify behavior for read, write, and owner permissions when the requester is not the owner; done means each permission level searches back only to resources the requester may access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100