Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add option to list configuration values optionally with origins #9930

Open
GadgetSteve opened this issue Sep 17, 2024 · 4 comments · May be fixed by #10035
Open

Add option to list configuration values optionally with origins #9930

GadgetSteve opened this issue Sep 17, 2024 · 4 comments · May be fixed by #10035
Assignees
@shubhamsugara22
Labels
Enhancement ✨ Improvement to a component Needs PR This issue is accepted, sufficiently specified and now needs an implementation
Milestone
4.0.0

Comments

@GadgetSteve
Copy link

GadgetSteve commented Sep 17, 2024 •
edited
Loading

Current problem

When trying to debug pylint configuration issues it can be difficult to identify what the current configuration values are and where they came from, (CLI or actual config file path). Given the multiple possible setting origins, many platform dependent, identifying the origin of many configuration settings can be challenging.

Desired solution

When I am trying to resolve configuration issues I would like to be able to issue commands such as pylint --config-list and pylint --config-list-show-origin - then when it is suspected that a configuration issue if any is causing problems (e.g. not detecting an issue on one users machine that is reported on another or by CI/CT).

Additional context

This would be similar to the git config list and git config list --show-origin command like options which I have often had to call upon to resolve issues with git.
@GadgetSteve GadgetSteve added the Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling label Sep 17, 2024
@Pierre-Sassoulas Pierre-Sassoulas added Enhancement ✨ Improvement to a component Needs PR This issue is accepted, sufficiently specified and now needs an implementation and removed Needs triage 📥 Just created, needs acknowledgment, triage, and proper labelling labels Sep 17, 2024
@Pierre-Sassoulas
Copy link
Member

Thank you for opening the issue. I like the similarity of the proposed command to what git have.

@shubhamsugara22
Copy link

@Pierre-Sassoulas are you working in this issue or enhancement , maybe i can have a crack at it

@GadgetSteve
Copy link
Author

@shubhamsugara22 I have been pushed for time to work on this so if you have the time available I am sure that any pull requests will be welcome and I will definitely make time to review, (as the originator of this issue), and add my input (which of course does not ensure that any such contributions will be used - that will be up to the core team).

@shubhamsugara22 shubhamsugara22 linked a pull request Oct 19, 2024 that will close this issue
Draft
@shubhamsugara22
Copy link

Created a Draft PR for now , going through structure and docs ,
if any refs are related to this issue would be appreciated & also any chat or channel for discussion
@Pierre-Sassoulas

@Pierre-Sassoulas Pierre-Sassoulas added this to the 4.0.0 milestone Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shubhamsugara22 shubhamsugara22

Labels
Enhancement ✨ Improvement to a component Needs PR This issue is accepted, sufficiently specified and now needs an implementation
Projects
None yet
Milestone
4.0.0
Development

Successfully merging a pull request may close this issue.

feat: Add option to list configuration values #9930 shubhamsugara22/pylint
3 participants
@Pierre-Sassoulas @GadgetSteve @shubhamsugara22