Standardize bang names based on new naming spec#403
Draft
FaFre wants to merge 5 commits intokagisearch:mainfrom
Draft
Standardize bang names based on new naming spec#403FaFre wants to merge 5 commits intokagisearch:mainfrom
FaFre wants to merge 5 commits intokagisearch:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, many bang names do not follow a specific pattern, and their names often fail to describe their actual behavior. This makes discovering the correct bang difficult when searching by name. Since I run a search on the names, this lead to a lot of false positives and confusion.
For example, the following bang applies a Spanish language tag, but you wouldn't know it just from looking at the name:
{ "s": "duckduckgo", "d": "duckduckgo.com", "t": "ddg-es", "u": "https://duckduckgo.com/?q={{{s}}}&kl=xl-es&kad=es_ES&ia=about", "c": "Online Services", "sc": "Search (non-US)" }To fix this, I created a naming specification to ensure bang names accurately reflect their function (such as including language or region tags): https://github.com/FaFre/bangs/blob/main/WEBSITE_NAMING_SPEC.md
I used an LLM to apply this spec across the repository in small batches. Therefore all of the renames are done by LLM and are not manually reviewed.
I am not sure if a PR of this size and impact is something that is welcomed to merge, so please let me know if there is interest. I could do this since I had a lot of tokens to burn. Another run (after maybe changes to the spec) will be not possible from my side.
Edit: I forgot to mention the PR also includes some removals of duplicate or nearly identical bangs...