SolidLabResearch / SolidLabResearch/user-managed-access
How to deal with prohibitions?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 3
Description
How to deal with them?
Currently, koreografeye is extended to return access modes that are allowed.
Should I ignore this for a first PoC? or add a return argument that does not allow certain access modes as a result of executing a koreografeye plugin.
(Copy of https://github.com/woutslabbinck/ucp-enforcement/issues/1 for preservation.)
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
The issue does not name files, tests, or an entry point. Start by locating the koreografeye extension and how plugins return allowed access modes, then clarify whether prohibitions belong in the first PoC; done means an agreed scope and documented behavior for disallowed access modes.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100