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
Trunk.io is an interesting tool for handling several linters and use them. It allows to describe with yaml files the linters to use in specific versions. If makes supports this tool, it will be more developer friendly and customizable for linters rules.
In this moment, you must go to makes' source code for knowing about mypy version, prospector version and every linter in builtins. With a yaml solution, the team can adapt even their local environment for warnings from CI linters (errors closer to developers).
Proposal
Implement a command for trunk.io as a new builtin (e.g. m . /lintCode <path_to_file>), reading a well-formatted trunk.io yaml for linting files in a repository.
About issue
Trunk.io is an interesting tool for handling several linters and use them. It allows to describe with yaml files the linters to use in specific versions. If makes supports this tool, it will be more developer friendly and customizable for linters rules.
In this moment, you must go to makes' source code for knowing about mypy version, prospector version and every linter in builtins. With a yaml solution, the team can adapt even their local environment for warnings from CI linters (errors closer to developers).
Proposal
Implement a command for trunk.io as a new builtin (e.g.
m . /lintCode <path_to_file>
), reading a well-formatted trunk.io yaml for linting files in a repository.Links / References
The text was updated successfully, but these errors were encountered: