How to deal with prohibitions?

Open
#10 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization

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.

Description

research UCP

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.)

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
4d 21h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SolidLabResearch/user-managed-access

All issues in SolidLabResearch/user-managed-access

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.