rspec/rules/S131/tsql/rule.adoc
Fred Tingaud 51369b610e
Make sure that includes are always surrounded by empty lines (#2270)
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.
2023-06-22 10:38:01 +02:00

50 lines
834 B
Plaintext

== Why is this an issue?
The requirement for a final ``++ELSE++`` clause is defensive programming. The clause should either take appropriate action, or contain a suitable comment as to why no action is taken.
=== Noncompliant code example
[source,sql]
----
SELECT
CASE category
WHEN 'A' THEN 21
WHEN 'B' THEN 33
END shipping_cost
FROM product
----
=== Compliant solution
[source,sql]
----
SELECT
CASE category
WHEN 'A' THEN 21
WHEN 'B' THEN 33
ELSE 42
END shipping_cost
FROM product
----
include::../see.adoc[]
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
=== Message
Add an "ELSE" clause to this "CASE" statement.
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]