[Feature request] String based configuration for "Excluded URLs and keys"
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Something like this
[
{"pattern": "https?://mail.google.com/*", "keys": ["h", "l"]},
{"pattern": "https?://example.com/*", "keys": ["/", "e"]}
]
Reason:
- easier to backup/copy configuration if you have like 100 patterns
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 the “Excluded URLs and keys” configuration and proposes a JSON array of pattern-and-keys objects, but it names no files, tests, or entry points. Start by locating the current configuration implementation and determine how the proposed format would be parsed, edited, persisted, and backed up; done means the format works for multiple patterns without breaking existing configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100