Just run ruff and return the output #1194
Conversation
Using the CLI to set include and ignore rules overrides whatever ruff configuration settings are present in a project (pyproject.toml, ruff.toml, etc). Most projects will choose to use those existing mechanisms to configure ruff, so having python-mode override them for settings in a user's vimrc will cause differences in ruff checks between a CLI run of ruff or a CI/CD pipeline, versus running PymodeLint.
|
This is a pretty crude PR - I stripped out a lot of functionality but it's what i'm driving daily now. I wanted to share to generate discussion. |
|
Thanks for the suggestion! :) As I've mentioned on the other PR, I totally agree with you that local configs should take full priority. And that leads us to three options:
WDYT? |
|
Ok, I've made a proposal.... take a look at this commit and let me know what you think about it :) |
|
@diraol I like the direction that you have gone with where vim configuration is a fallback method, or possibly merging. Let me give your branch a try. Thank you for taking feedback! |
2 participants
Using the CLI to set include and ignore rules overrides whatever ruff configuration settings are present in a project (pyproject.toml, ruff.toml, etc).
Most projects will choose to use those existing mechanisms to configure ruff, so having python-mode override them for settings in a user's vimrc will cause differences in ruff checks between a CLI run of ruff or a CI/CD pipeline, versus running PymodeLint.