nuts-foundation / nuts-foundation/nuts-node
Decide/implement whether metadata needs to be cached
Open
Nobody has claimed this yet.
openid4vci
prio: low
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Now it's re-retrieved every time it is required.
Could be sped up (and made slightly more robust) if we cache it.
(but consider pros/cons)
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
No file, test, or entry point is named. Start by locating where metadata is re-retrieved and assess cache lifetime, invalidation, consistency, and failure trade-offs before proposing an approach. Done means the caching decision is documented and, if adopted, the implementation and relevant tests cover the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100