-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: print ruff config #3177
Comments
Can you try |
This works! actually it's perhaps too verbose, including formatting and values not optimized for quick developer troubleshooting, like:
I would add that I didn't see the source file used to generate the config, but it seems consistent with my I also now see this flag ( I think I passed over it because I was looking for a substring like I also see this flag is enabled at the top level but not mentioned under the top level info at overall, it seems my concern is basically handled and this issue can be closed. optionally, we can enhance some of those points above which are basically nits 3 optional nits recap:
|
Yeah we used to manually omit some of that |
I thought we did show where the config came from but doesn't look like it. |
Let's leave this open since there are a few things to improve here. We can't really change |
Fixed one of these issues, tracking the other in #3202. |
as a developer, I'd like the ability to print the ruff config so that I can better troubleshoot whether an issue is a local config issue or a geniune bug in ruff
related issue where I ran into this troubleshooting limitation: #3174
I have no particular opinion on the cli command syntax but let me propose a new
ruff log config
command for nowThis command would print the config path used (whether pyproject.toml or something else), the python target version, selected rulesets, ignored rule information, and all of the other content that would normally be written inside the config file
this feature should also be documented clearly within https://beta.ruff.rs/docs/configuration/
possibly this print command could be added to the github ruff issue template as it will also probably assist in issue resolution
thanks!
The text was updated successfully, but these errors were encountered: