Javascript check question： import eslint json report is ok, but bugs is inconrrent, less more

[shwull]

Template for a good bug report, formatted with Markdown:

• versions used (SonarQube, Scanner, Plugin, and any relevant extension)
  sonarqube 7.6, is installed on window 64
  scanner: sonar-scanner-4.6.2.2472-windows
  plugin:none

• error observed (wrap logs/code around triple quote ``` for proper formatting)
  no

• steps to reproduce

1. create eslint json file
   

   

2. create related to report.html

   

3. on windows bash command: sonar-scanner -Dsonar.projectKey=eslint_cms -Dsonar.projectName=eslint_cms -Dsonar.sources=./src -Dsonar.eslint.reportPaths=eslint.json
   

   
   
   4）view result on sonarqube web
   
   

• potential workaround
  it is eslint.jsoneslint.json (1.0 MB)
  related to report.html Processing: result.html…

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

[Colin]

Hey there.

First things first, SonarQube v7.6 is way past EOL. You should upgrade to v7.9 LTS and then v8.9 LTS (and optionally onward to v9.0.1) to be supported in this community.

Can you point to at least one specific issue in the report you expect to be shown as a bug in SonarQube, that is not?

[shwull]

ok I will use newer version, thank you