rspec/rules/S1764/plsql/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

53 lines
1.1 KiB
Plaintext

== Why is this an issue?
Using the same value on either side of a binary operator is almost always a mistake. In the case of logical operators, it is either a copy/paste error and therefore a bug, or it is simply wasted code, and should be simplified.
This rule ignores operators ``+``, ``++*++`` and ``++||++``, and expressions: ``++1=1++``, ``++1<>1++``, ``++1!=1++``, ``++1~=1++`` and ``++1^=1++``.
=== Noncompliant code example
[source,sql]
----
SELECT code
FROM Person
WHERE first_name IS NULL OR first_name IS NULL; -- Noncompliant
SELECT * FROM Users
INNER JOIN Clients ON Clients.id = Clients.id; -- Noncompliant
----
=== Compliant solution
[source,sql]
----
SELECT code
FROM Person
WHERE first_name IS NULL OR last_name IS NULL;
SELECT * FROM Users
INNER JOIN Clients ON Clients.id = Users.id;
----
include::../exceptions.adoc[]
include::../see.adoc[]
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
include::../highlighting.adoc[]
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]