Consider adding the option for custom patterns?

[ColinEberhardt]

When spell checking a recent blog post, I had to add a lot of ignores due to filenames being referenced in plain text within the the blog post:

https://github.com/ColinEberhardt/blog/commit/2f65135f14e466ffd59ab922b15ff74903a54ff2#diff-b9a2754b5f195f0113dc72bd305fcdb3R986

I often surround filenames in back-ticks, but they aren't strictly speaking code, so I can understand why people would leave them plain text.

It would be great if I could add a few regex patterns via the spell checker configuration to exclude these patterns.

[lukeapage]

you could use this to specify the current ignores as well, so for example the -n option wasn't needed if defined in the .spelling

[lokeshdaiya]

Is there any solution to ignore some text based on patterns?

b67808 k989jk9 jk890Kl

I want to ignore these kind of strings.

Are you going to add any option to ignore text based on patterns?

[mamat-rahmat]

The custom regex pattern for parts to ignoring is really needed. Every project may have their specific parts that they don't want to included spellchecking. Like markdown that using non-standard codeblock syntax.

[PatMyron]

Regex support in .spelling would be amazing

Regex could have covered past functionality like --ignore-numbers and --ignore-acronyms

regex support solves these:

https://github.com/lukeapage/node-markdown-spellcheck/issues/99 https://github.com/lukeapage/node-markdown-spellcheck/issues/95 https://github.com/lukeapage/node-markdown-spellcheck/issues/89 https://github.com/lukeapage/node-markdown-spellcheck/issues/35 https://github.com/lukeapage/node-markdown-spellcheck/issues/9

Future requests like ignoring usernames and ignoring long "words" like API keys would be solved too

[plaindocs]

This looks like it has a regex element https://www.npmjs.com/package/simple-spellchecker