Store current user query/queries
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
- typescript
- Domain
- authentication, database, full-stack
Research direction
Start by tracing where the in-memory userId-to-queryId mapping is created and read, then inspect how better-auth currently persists data. Decide whether browser localStorage or backend database storage meets the security requirements; done means mappings survive a container restart without exposing user data.
Written by the indexing model from the issue text.
Description
Currently the mapping of userId to queryId is only stored in memory and doesn't survive a container restart. We should store it either in localStorage of the browser or in a database (maybe the same we're using for better-auth) on the backend. This might have security implications.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 22h 6m
- Merged PRs (30d)
- 12
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.
More from stackabletech/cockpit
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
stackabletech/cockpit#312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
stackabletech/cockpit#224 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
stackabletech/cockpit#101 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
stackabletech/cockpit#313 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
stackabletech/cockpit#310 ·
All issues in stackabletech/cockpit
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100