graphprotocol / graphprotocol/hypergraph
Reconsider if Account & Identity should be one DB row
Open
Nobody has claimed this yet.
Chore
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
This depends if we have one global Identity per Account or multiple Identities e.g. per App.
In any keys the keyBoxes related to the encryption key of the Identity and therefor should be moved there.
source: https://github.com/geobrowser/graph-framework/pull/64#discussion_r1907135646
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 reading the discussion linked in the issue, especially the assumptions about one global Identity per Account versus multiple Identities per App and the placement of keyBoxes. Done means reaching and documenting a decided Account/Identity database model and identifying the resulting schema changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100