rspec/rules/S1116/comments-and-links.adoc

=== is related to: S3955

=== is related to: S1763

=== relates to: S906

=== is related to: S901

=== on 10 Jul 2013, 14:32:54 Dinesh Bolkensteyn wrote:
Implemented by: \http://jira.codehaus.org/browse/SONARJAVA-201

=== on 10 Jul 2013, 14:42:28 Dinesh Bolkensteyn wrote:
I decreased the severity from Critical to Major, because of the following cases:


----
for (..); // Empty statement as the for body
int a = 0;; // Simply a styling issue
----

=== on 29 Oct 2013, 13:16:20 Freddy Mallet wrote:
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3210 for Flex

=== on 12 Feb 2014, 17:55:47 Freddy Mallet wrote:
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3450 for PHP

=== on 30 Jan 2019, 13:45:37 Amaury Levé wrote:
Marked as irrelevant for VB.NET because the ROI for its implementation is really low. Also, there is a ``++EmptyStatement++`` syntax kind it doesn't call back on the expected cases so we would need a trivia analysis which is quite costly. As the only 2 cases, we could catch are 2 colons or a colon with nothing else on the line (which are low value cases) we decided to ignore this rule.
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== is related to: S3955`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== is related to: S1763`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== relates to: S906`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== is related to: S901`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00
Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== on 10 Jul 2013, 14:32:54 Dinesh Bolkensteyn wrote:`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			`Implemented by: \http://jira.codehaus.org/browse/SONARJAVA-201`

Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== on 10 Jul 2013, 14:42:28 Dinesh Bolkensteyn wrote:`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			`I decreased the severity from Critical to Major, because of the following cases:`


			`----`
			`for (..); // Empty statement as the for body`
			`int a = 0;; // Simply a styling issue`
			`----`

Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== on 29 Oct 2013, 13:16:20 Freddy Mallet wrote:`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			`Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3210 for Flex`

Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== on 12 Feb 2014, 17:55:47 Freddy Mallet wrote:`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			`Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3450 for PHP`

Fix the comment display: rule-id, timestamp, GH visibility, link direction 2021-06-03 09:05:38 +02:00			`=== on 30 Jan 2019, 13:45:37 Amaury Levé wrote:`
Export comments and rspec-to-rspec links from jira 2021-06-02 20:44:38 +02:00			Marked as irrelevant for VB.NET because the ROI for its implementation is really low. Also, there is a ``++EmptyStatement++`` syntax kind it doesn't call back on the expected cases so we would need a trivia analysis which is quite costly. As the only 2 cases, we could catch are 2 colons or a colon with nothing else on the line (which are low value cases) we decided to ignore this rule.