graphprotocol / graphprotocol/hypergraph
improve create space flow
Open
Nobody has claimed this yet.
Chore
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
You should be able to provide a name and this name should be encrypted.
When listing spaces the name should be decrypted and accessible to the client.
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 locating the create-space entry point and the code that lists spaces. Trace how a space name currently moves between the client and storage, then identify the existing encryption utilities and related tests. Done means creation accepts a name, the stored name is encrypted, and listing spaces returns the decrypted name to the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100