26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
|
=== On 2015-03-20T13:07:59Z Tamas Vajk Wrote:
|
||
|
|
This is the first draft of this rule, I don't know which properties need to be set. (SQALE, tags, ...)
|
||
|
|
|
||
|
|
=== On 2015-03-20T13:21:20Z Ann Campbell Wrote:
|
||
|
|
\[~tamas.vajk] if you'll expand the description to include the reasons (bad thing that will happen if you break the rule or good thing that will happen if you follow it) that will help me with filling in the other fields.
|
||
|
|
|
||
|
|
=== On 2015-04-10T08:09:30Z Tamas Vajk Wrote:
|
||
|
|
Ann, I've added an exception to this rule, could you please check it?
|
||
|
|
|
||
|
|
Thanks
|
||
|
|
|
||
|
|
=== On 2015-04-10T12:10:12Z Ann Campbell Wrote:
|
||
|
|
The exception looks fine, but I think it would be helpful if you added a small code sample.
|
||
|
|
|
||
|
|
You can use a "// Compliant" or "// Ignored" comment to mark the line that's being ignored.
|
||
|
|
|
||
|
|
=== On 2015-04-13T12:50:55Z Tamas Vajk Wrote:
|
||
|
|
\[~ann.campbell.2]: [~dinesh.bolkensteyn] asked for a more meaningful example, so I updated the description.
|
||
|
|
|
||
|
|
=== On 2015-05-11T12:11:49Z Tamas Vajk Wrote:
|
||
|
|
Added the code sample as well to the Exception
|
||
|
|
|
||
|
|
=== On 2015-05-11T14:03:33Z Ann Campbell Wrote:
|
||
|
|
thanks [~tamas.vajk]
|
||
|
|
|