feat: Implement a store

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
authorization

Research direction

Start by examining the Authorizer struct and its current responsibilities. The issue does not identify files, tests, or the store's required operations, so clarify the abstraction's scope for cached delegations and stored revocations before implementation. Done should be defined by agreed requirements and accompanying tests.

Written by the indexing model from the issue text.

Description

The Authorizer struct might potentially want access to cached delegations or stored revocations in the future.

For this we need a store abstraction.

Dominant language
Rust
Stars
27
Forks
4
Avg merge
1h 24m
Merged PRs (30d)
2

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 n0-computer/rcan

All issues in n0-computer/rcan

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.