-
Notifications
You must be signed in to change notification settings - Fork 127
Typos reports typos in _typos.toml #711
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
You can ignore the config files if you create a
|
Yeah, I can also add it to [default.extend-words]
grey = "gray"
[files]
extend-exclude = ["_typos.toml"] it just feels a bit silly that the default behavior is that |
There are a couple of ways for us to fix this
Any thoughts on what approach to take? |
For me it makes sense to hard-code |
Agree, why people want to check for typos the |
This doesn't use `extend-exclude` which means that `typos typos.toml` will stil be skipped This doesn't just skip the currently loaded config but any file name that looks like a config, which might be a big aggressive but allows us to do layered config in the future.... We've been saying that for a while. Fixes crate-ci#711
This doesn't use `extend-exclude` which means that `typos typos.toml` will stil be skipped This doesn't just skip the currently loaded config but any file name that looks like a config, which might be a big aggressive but allows us to do layered config in the future.... We've been saying that for a while. Fixes crate-ci#711
Adding your own
extend-words
is quite problematic:I would suggest typos ignore its own configuration file when checking for typos
The text was updated successfully, but these errors were encountered: