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

Update RSPEC metadata + rules in SonarWay #1664

Merged
merged 2 commits into from
Aug 13, 2018

Conversation

Evangelink
Copy link
Contributor

Fix #1663
Fix #1662
Fix #1661
Fix #1660
Fix #1658

@Evangelink Evangelink requested a review from valhristov August 10, 2018 15:38
@ghost ghost assigned Evangelink Aug 10, 2018
@ghost ghost added the Status: Needs Review label Aug 10, 2018
Copy link
Contributor

@andrei-epure-sonarsource andrei-epure-sonarsource left a comment

Choose a reason for hiding this comment

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

I think RSPECs should be updated for S4524 and S4144

@@ -10240,7 +10240,7 @@
<value>switch can contain a default clause for various reasons: to handle unexpected values, to show that all the cases were properly considered.</value>
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this should be updated as well (locally, for me, it's updated)

@@ -3262,7 +3262,7 @@
<value>Attackers can use widely-available tools to view cookies and read any sensitive information they may contain. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.</value>
</data>
<data name="S2255_IsActivatedByDefault" xml:space="preserve">
<value>False</value>
<value>True</value>
</data>
<data name="S2255_Remediation" xml:space="preserve">
<value>Constant/Issue</value>
Copy link
Contributor

Choose a reason for hiding this comment

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

For <data name="S4144_Description" xml:space="preserve">, locally I have

When two methods have the same implementation, either it was a mistake - something else was intended - or the duplication was intentional, but may be confusing to maintainers. In the latter case, one implementation should invoke the other.

@andrei-epure-sonarsource
Copy link
Contributor

Update: the changes which I reported in my previous comments must be reviewed, because they may imply a change in behavior which may have to be implemented before updating the RSPEC.

@andrei-epure-sonarsource andrei-epure-sonarsource merged commit 0050d01 into master Aug 13, 2018
@ghost ghost removed the Status: Needs Review label Aug 13, 2018
@andrei-epure-sonarsource andrei-epure-sonarsource deleted the ammo/metadata branch August 13, 2018 08:34
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