Feature: Custom search completion providers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Search completions are a useful feature, but are currently limited to the builtin engines. Only a handful of popular search engines and a couple mysteriously niche ones have been blessed with inclusion, other submissions have been rejected or ignored: #2590 #3851 #3981 #4091 #4094 #4189 #4238
These PRs should be accepted - with the condition "I will not fix this if it breaks" if necessary - but failing that, the ability to configure custom completion providers should be added.
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
Start with background_scripts/completion_engines.js and review how the built-in providers are defined and selected. Determine how custom providers could be configured without removing existing engines; done means users can add them and the cited provider submissions no longer require hard-coded inclusion.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100