2021-06-03 09:05:38 +02:00
=== relates to: S1144
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
=== is related to: S3985
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
=== relates to: S895
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
=== on 15 Oct 2013, 08:45:25 Freddy Mallet wrote:
2021-06-02 20:44:38 +02:00
Is implemented by \http://jira.codehaus.org/browse/SONARJAVA-358
2021-06-03 09:05:38 +02:00
=== on 16 Oct 2013, 23:52:16 Ann Campbell wrote:
2021-06-02 20:44:38 +02:00
I've added Compliant Solutions, but someone should double-check my guess at PL/SQL
2021-06-03 09:05:38 +02:00
=== on 22 Oct 2013, 14:45:38 Freddy Mallet wrote:
2021-06-02 20:44:38 +02:00
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3195 in Flex
2021-06-03 09:05:38 +02:00
=== on 9 Dec 2013, 08:37:03 Dinesh Bolkensteyn wrote:
2021-06-02 20:44:38 +02:00
The PL/SQL case is not a field, but just a local variable (for which we have another rule, I'll remove it for now.
2021-06-03 09:05:38 +02:00
=== on 9 Dec 2013, 08:45:12 Dinesh Bolkensteyn wrote:
2021-06-02 20:44:38 +02:00
I guess that we need to allow any annotated private field? - in fact perhaps not, I can imagine that some private fields are injected, but read from outside?
2021-06-03 09:05:38 +02:00
=== on 23 Feb 2014, 22:51:34 Freddy Mallet wrote:
2021-06-02 20:44:38 +02:00
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3505 for PHP
2021-06-03 09:05:38 +02:00
=== on 10 Mar 2017, 14:32:45 Ann Campbell wrote:
2021-06-02 20:44:38 +02:00
Irrelevant for C# because fields are covered in the language's implementation of RSPEC-1144
2021-06-03 09:05:38 +02:00
=== on 5 Nov 2019, 10:54:34 Nicolas Harraudeau wrote:
2021-06-02 20:44:38 +02:00
Python fields only exist once they are set. Thus RSPEC-4487 is more appropriate.