Extended Storage (per domain)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
An easy way to the Storage implementation to support site based preferences instead of global.
Is your feature request related to a bug?
N/A
What are the alternatives?
No alternatives available, as far as I know.
Additional context
Some extensions may have some preferences where a simple array of domains as items is enough. For example, adblocking... An option to "disable for this website" is pretty simple to make.
However, creating a Storage implementation inside of WXT that supports global and per domain functionality, might be amazing. I'm personally in a need of this feature as my extension offers a handful of options where each one works globally atm, but it makes more sense that each one works per domain instead.
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
The issue names no files, tests, or entry points. Start by locating the existing Storage implementation and determine how global preferences are represented before defining per-domain behavior. Done should include a decided API and coverage for both global and domain-specific preferences, including the disable-for-this-website case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100