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.

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

Create configuration templates with message tiers or presets #7120

Open
Pierre-Sassoulas opened this issue Jul 4, 2022 · 1 comment
Open
Labels
Enhancement ✨ Improvement to a component Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc.

Comments

@Pierre-Sassoulas
Copy link
Member

Current problem

Pylint do not permit to use a preset configuration like some tool like eslint so the configuration is lengthy and often copy pasted.

Desired solution

Something that permits to expands on a sane configuration depending on your project and easily share a configuration. I.e. data science project would have x,y,z in good-names, but not web-project, etc.

Additional context

This is a new issue so we can close #746 that had a lot of other things in it see #746 (comment). It was also discussed at length in #3512. See also #6968

@Pierre-Sassoulas Pierre-Sassoulas added Enhancement ✨ Improvement to a component Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc. labels Jul 4, 2022
@sisp
Copy link
Contributor

sisp commented Jul 11, 2022

As an addition to a preset configuration, I think shareable configurations would help standardize configurations, e.g. in large corporate environments. With shareable configurations, best practices can be configured in a central place and updates to those configurations can be obtained by package updates in downstream projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ✨ Improvement to a component Needs specification 🔐 Accepted as a potential improvement, and needs to specify edge cases, message names, etc.
Projects
None yet
Development

No branches or pull requests

2 participants