Access Control / Permissions
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
A very fine project!
I'm new to OT/CRDT, and I was wondering how/if a (central) user/role/group permission based access control can be added?
For example, for a Notes PoC. Also, how would conflicts like these be handled?
- Member C adds a
note Test. Member D opens it. - Member D disconnects X
- Member C sets the
note Testtoprivate(not accessible by D) - Member D makes edits on
note Test, and various other edits toother notes - Member D reconnects to the server
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 identify files, tests, or an implementation entry point. Begin by reviewing the Notes PoC scenario and clarifying how permission changes should interact with offline edits and reconnection. Done would require an agreed access-control design and documented behavior for the listed conflict case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100