-
I'm using typos mostly as a pre-commit hook for Markdown documentation through pre-commit-hooks.nix. I have worked on the According to this section in typos' README, to get rid of false-positives, I have to create a In many projects it is not desired to have an additional configuration file, especially one that is only for configuring tooling like a pre-commit hook and isn't hidden, like for example Is there a way to extend the word list through a command line argument or any other way that does not require creating this file? Is this something I should open an issue for? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Lack of CLI configurability is an intentional design choice to ensure people get consistent runs on the same repo, ie its project configuration. In a way, you are shifting the project configuration to another location and that is aligned with our goals but I'm still hesitant to open the door on this. A workaround would be to have your hook write the settings to a temp dir and to use |
Beta Was this translation helpful? Give feedback.
Lack of CLI configurability is an intentional design choice to ensure people get consistent runs on the same repo, ie its project configuration.
In a way, you are shifting the project configuration to another location and that is aligned with our goals but I'm still hesitant to open the door on this. A workaround would be to have your hook write the settings to a temp dir and to use
--isolated --config <path>
.