feat: add raw-query option for search bangs #896
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new optional
raw-queryflag for search bangs, giving users control over whether{QUERY}is URL encoded before being inserted into the bang URL.What this changes
raw-query: booleanto the bang configuration schema.falseto preserve the existing behavior.raw-query: true,{QUERY}is substituted as-is, withoutencodeURIComponent.configuration.md)search.html)page.js)widget-search.go)Why
This resolves issue #527, allowing certain shortcuts to receive an unencoded path-style query. This is especially useful for URLs where slashes or special characters are meaningful, such as GitHub paths.