Move sensitive user data from localStorage into the DB
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by tracing where connection data, SQL queries, and history are written to and read from localStorage, then inspect the existing database access path. Keep user preferences such as the chosen theme in localStorage and move sensitive data into the database; done when those sensitive values persist there instead. The issue names no files or tests, so identify the relevant entry points before estimating the change.
Written by the indexing model from the issue text.
Description
A lot of user data is saved in localStorage. This includes connection data, full sql queries and history.
Sensitive parts should be moved into the database while user preferences like the chosen theme can stay.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 39
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 68/100
stackabletech/cockpit#444 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stackabletech/cockpit#385 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
stackabletech/cockpit#465 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
stackabletech/cockpit#462 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
stackabletech/cockpit#461 ·
Maintainers usually reply within 2 days
All issues in stackabletech/cockpit
Similar issues
-
bug parity
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WenyuChiou/agent-board#1489 ·
Maintainers usually reply within 1 day
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
bug good first issue P4 size:S web-ui
Difficulty 2/5 Half a day Newbie friendliness 85/100
josephfung/curia#2600 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cloudflare/partykit#444 ·