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.
37 lines
946 B
Plaintext
37 lines
946 B
Plaintext
== Why is this an issue?
|
|
|
|
:operationName: method
|
|
:emptyCode: vbnet/empty-code.adoc
|
|
:notsupportedCode: vbnet/notsupported-code.adoc
|
|
:notimplementedCode: vbnet/notimplemented-code.adoc
|
|
:commentCode: vbnet/comment-code.adoc
|
|
|
|
include::../why-dotnet.adoc[]
|
|
|
|
=== Exceptions
|
|
|
|
The following empty methods are considered compliant:
|
|
|
|
* empty `Overridable` methods, as the implementation might not be required in the base class
|
|
* empty methods that override a `MustOverride` method as the implementation is mandatory for child class
|
|
* empty overrides in test assemblies for mocking purposes
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
=== Message
|
|
|
|
Add a nested comment explaining why this method is empty, throw a NotSupportedException or complete the implementation.
|
|
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|