51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
28 lines
698 B
Plaintext
28 lines
698 B
Plaintext
== Why is this an issue?
|
|
|
|
The cyclomatic complexity of methods should not exceed a defined threshold.
|
|
|
|
Complex code can perform poorly and will in any case be difficult to understand and therefore to maintain.
|
|
|
|
=== Exceptions
|
|
|
|
While having a large number of fields in a class may indicate that it should be split, this rule nonetheless ignores high complexity in ``++equals++`` and ``++hashCode++`` methods.
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
include::../parameters.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|