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

Improve information to be able to resolve issues #13

Open
hbrtcnes opened this issue Dec 7, 2022 · 0 comments
Open

Improve information to be able to resolve issues #13

hbrtcnes opened this issue Dec 7, 2022 · 0 comments

Comments

@hbrtcnes
Copy link

hbrtcnes commented Dec 7, 2022

Is your feature request related to a problem? Please describe.

When there is an issue in SonarQube, no details are available (here for rule PYLINT:W9095) when clicking "Why is it an issue?" :
image

Describe the solution you'd like

It would be nice to have details for all the rules (why is it an issue) and an example describing what is expected.

  • For example, for the rule PYLINT:W9095, we don't have enough details to find the expected format:
    image
    It would be nice to have an example with the expected format, when clicking "Why is it an issue?".

  • For example, for the rule PYLINT:R5403,
    image
    It would be nice to know why it is better to use argparse module, in what context (not when just passing arguments maybe).

  • For example, for the rule PYLINT:R5401,
    image
    It would be nice to know why consider dropping sys.exit() and how to replace it.

Versions

  • cnes-pylint-extension: 6.0.0
  • sonarQube: Community Edition Version 8.9.6 (build 50800)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant