Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to add additional custom wordlist #187

Open
GlenDC opened this issue Oct 26, 2021 · 0 comments
Open

ability to add additional custom wordlist #187

GlenDC opened this issue Oct 26, 2021 · 0 comments

Comments

@GlenDC
Copy link

GlenDC commented Oct 26, 2021

First of all thank you for your hard work. I also tried to look for what I was looking for in the existing open and closed issues but couldn't really find it. If it is a duplicate issue please do close immediately and link to it. My apologies if so.

It would be very useful if I could add a wordlist to the root of a project to add additional words that should be accepted. This is often for technical words or words for historic reasons. In HTTP headers it is for example quite custom to have words that look like misspellings but are actually correct. Some examples:

  • Ect, not a misspelling for etc, it's an abbreviation short for "effective connection type";
  • Referer instead of Referrer: this is a misspelling, but so on purpose, as the ones making the HTTP spec made that mistake a long time ago, and now we all have to live with it;

There are a lot more examples. I use this project (misspell) as part of golang-ci by the way. Currently there are 2 options I have:

  • ignore misspell for an entire file, project: not desired as I do like the linting it gives me in general;
  • add nolint:misspell for each line where such a word occurs: this is what I currently do, but it adds a lot of noise, while really it is always about the same small set of words for any given project;

I imagine I am not the only person suffering from this. As such I have a feeling that this is probably already possible, but the documentation seemed to indicate the oppose (and so by design). Any help here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant