Uploaded image for project: 'SonarLint for Visual Studio Code'
  1. SonarLint for Visual Studio Code
  2. SLVSCODE-274

Only analyze Python files owned by the user

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      SonarLint analyzes any open file, so it could happen that one comes from the Python standard library, for example when following an import directive, or from a third-party library.

      We shouldn't raise issues for those kind of files, as they are not actionable by the user and they bring noise in the diagnostics view (and there are usually a big number of issues for those files...).

      In some cases sources of 3rd party libraries can be located in the workspace (with the venv mechanism), so excluding files outside the workspace would only work for the standard lib.

      As a side note, Pylint has the same behavior.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            damien.urruty Damien Urruty
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: