You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have the entire configuration for typos shared among multiple repositories as a base, and be able to override those options locally after inheriting.
It would be nice if there was an option in the config file to extend from another config file, much like ruff or pyright does.
Currently, for ruff, I can for example do something like this in my pyproject.toml (docs)
In regards to #931, supporting something like this would allow people to write/generate their own files like false_positives.toml which they can then include/share as well, and you don't have to support some additional format for config
#193 is our issue for layered config but that is more focused on implicitly extending directories above the current one, rather than specifying them from another location.
Personally, I use a template repo for keeping everything in sync (see https://github.com/epage/_rust) as most tools do not support the type of extension needed for centralizing like this and supporting it in every tools seems like it could get messy.
I'd like to have the entire configuration for typos shared among multiple repositories as a base, and be able to override those options locally after inheriting.
It would be nice if there was an option in the config file to extend from another config file, much like
ruff
orpyright
does.Currently, for
ruff
, I can for example do something like this in mypyproject.toml
(docs)For
typos
, I would expect it to look something likeWhere the locale inherited from the submodule's typos.toml would be overwritten by the locally declared
en-gb
This would imply the following order for sourcing:
The text was updated successfully, but these errors were encountered: