-
Notifications
You must be signed in to change notification settings - Fork 79
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
Clean code attributes and better descriptions complying with Sonar Coding rule guidelines #349
base: main
Are you sure you want to change the base?
Changes from all commits
c3ca195
bd8a4f1
706c181
06e0173
dabb897
a0a2c2e
f23f81d
613a418
3975cd0
7d53fc2
0fa8fc7
a3add9e
52c0d78
abfcfea
94c42dc
8470f60
f714c48
7b43fe8
ffa58e8
ee7f507
f2f8eff
3d2e6c8
4973db6
d6dbc50
14b4072
7fc9af0
3d041ce
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"title": "Avoid Spring repository call in loop or stream operations", | ||
"title": "Spring repository should not be called in loop or stream operations", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. in my point of view, I prefer a turn of phrase without negation, thus, I prefer "avoid" than "should not be" ... but I can ask for the point of view of core team There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. From Sonar Coding rule guidelines:
And as a developer I like the "X should [ not ] Y" pattern, because the expected fix is clear. |
||
"type": "CODE_SMELL", | ||
"status": "ready", | ||
"remediation": { | ||
|
@@ -9,8 +9,14 @@ | |
"tags": [ | ||
"performance", | ||
"spring", | ||
"eco-design", | ||
"sustainability", | ||
"creedengo" | ||
], | ||
"defaultSeverity": "Minor" | ||
"defaultSeverity": "Minor", | ||
"code": { | ||
"impacts": { | ||
"RELIABILITY": "LOW" | ||
}, | ||
"attribute": "EFFICIENT" | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,21 @@ | ||
{ | ||
"title": "Avoid using unoptimized vector images", | ||
"title": "Unoptimized vector images should be avoided", | ||
"type": "CODE_SMELL", | ||
"status": "ready", | ||
"remediation": { | ||
"func": "Constant\/Issue", | ||
"constantCost": "60min" | ||
}, | ||
"tags": [ | ||
"eco-design", | ||
"creedengo" | ||
"sustainability", | ||
"creedengo", | ||
"performance" | ||
], | ||
"defaultSeverity": "Minor" | ||
"defaultSeverity": "Minor", | ||
"code": { | ||
"impacts": { | ||
"RELIABILITY": "LOW" | ||
}, | ||
"attribute": "EFFICIENT" | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all these pom.xml modifications must be in the ecocode-rules-specifications pom.x instead and the current parent pom.xml
all other plugins work with java 17. why do you put java 11 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
POM changes have been moved to ecocode-rules-specifications.
Some of the configuration, including java 11 is coming from
https://github.com/green-code-initiative/ecoCode-java/blob/main/pom.xml
Java version could be changed.