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

[suricate] update sonar project metrics and new project coverage #45

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mauricou88
Copy link

in sonar/project metrics, add the coverage code

create a new project coverage metrics for the new code ( only the new code is concerned by the modifcation)

Copy link
Contributor

@loicgreffier loicgreffier Jun 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be the image of the project-coverage widget itself, not the metrics widget

usageExample: 'My branch'
required: false
-
name: 'SURI_PULL_REQUEST'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indentation should be fixed (I know it is not fixed in every widget)

@@ -0,0 +1,4 @@
name: Metrics
description: Display the selected Sonar metrics of a new code in an application
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New widget is only related to coverage, right? If yes, update the description so it specifies it only display Sonar coverage metrics

@@ -0,0 +1,4 @@
name: Metrics
description: Display the selected Sonar metrics of a new code in an application
technicalName: sonar
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technical name should be more precise (and unique), something like sonarProjectCoverage

@@ -0,0 +1,57 @@
.widget.sonar {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After updating the technical name, think about updating CSS classes righ there

Copy link
Contributor

@loicgreffier loicgreffier Jun 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was not intended to be committed I guess 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants