31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
|
=== Related: RSPEC-1144
|
|||
|
|
|
|||
|
|
=== Related: RSPEC-3985
|
|||
|
|
|
|||
|
|
=== Relates: RSPEC-895
|
|||
|
|
|
|||
|
|
=== On 2013-10-15T08:45:25Z Freddy Mallet Wrote:
|
|||
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARJAVA-358
|
|||
|
|
|
|||
|
|
=== On 2013-10-16T23:52:16Z Ann Campbell Wrote:
|
|||
|
|
I've added Compliant Solutions, but someone should double-check my guess at PL/SQL
|
|||
|
|
|
|||
|
|
=== On 2013-10-22T14:45:38Z Freddy Mallet Wrote:
|
|||
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3195 in Flex
|
|||
|
|
|
|||
|
|
=== On 2013-12-09T08:37:03Z Dinesh Bolkensteyn Wrote:
|
|||
|
|
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.
|
|||
|
|
|
|||
|
|
=== On 2013-12-09T08:45:12Z Dinesh Bolkensteyn Wrote:
|
|||
|
|
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?
|
|||
|
|
|
|||
|
|
=== On 2014-02-23T22:51:34Z Freddy Mallet Wrote:
|
|||
|
|
Is implemented by \http://jira.codehaus.org/browse/SONARPLUGINS-3505 for PHP
|
|||
|
|
|
|||
|
|
=== On 2017-03-10T14:32:45Z Ann Campbell Wrote:
|
|||
|
|
Irrelevant for C# because fields are covered in the language's implementation of RSPEC-1144
|
|||
|
|
|
|||
|
|
=== On 2019-11-05T10:54:34Z Nicolas Harraudeau Wrote:
|
|||
|
|
Python fields only exist once they are set. Thus RSPEC-4487 is more appropriate.
|
|||
|
|
|