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

[Javascript/Daemon] Issues should use the severity specified in the Quality Profile #1385

Closed
duncanp-sonar opened this issue May 5, 2020 · 1 comment
Labels
Area: Connected Mode Area: Daemon BLOCKED Blocked - dependent on another ticket being fixed first Language: JS Related to JavaScript Type: Improvement

Comments

@duncanp-sonar
Copy link
Contributor

duncanp-sonar commented May 5, 2020

Description

See #808 [C#/VB] Issues should use the severity specified in the Quality Profile.

The JavaScript analyzer/daemon has the same issue.

At present the severity is hard-coded to Warning here the sseverity is incorrect in both standalone mode and connected mode.

NOTE: currently blocked:

  • we don't currently support connected mode for JavaScript

Parent issue: #884

@duncanp-sonar duncanp-sonar added Type: Improvement Area: Connected Mode Area: Daemon Language: JS Related to JavaScript BLOCKED Blocked - dependent on another ticket being fixed first labels May 5, 2020
@duncanp-sonar duncanp-sonar changed the title [Javascript/Daemon] Issues should use the severity specified in the Quality [Javascript/Daemon] Issues should use the severity specified in the Quality Profile May 6, 2020
@rita-gorokhod
Copy link
Contributor

Outdated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Connected Mode Area: Daemon BLOCKED Blocked - dependent on another ticket being fixed first Language: JS Related to JavaScript Type: Improvement
Projects
None yet
Development

No branches or pull requests

2 participants