rspec/rules/S1939/java/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

66 lines
1.1 KiB
Plaintext

== Why is this an issue?
All classes extend ``++Object++`` implicitly. Doing so explicitly is redundant.
Further, declaring the implementation of an interface _and_ one if its parents is also redundant. If you implement the interface, you also implicitly implement its parents and there's no need to do so explicitly.
=== Noncompliant code example
[source,java]
----
public interface MyFace {
// ...
}
public interface MyOtherFace extends MyFace {
// ...
}
public class Foo
extends Object // Noncompliant
implements MyFace, MyOtherFace { // Noncompliant
//...
}
----
=== Compliant solution
[source,java]
----
public interface MyFace {
// ...
}
public interface MyOtherFace extends MyFace {
// ...
}
public class Foo implements MyOtherFace {
//...
}
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
=== Message
"yyy" is a "xxx" so "xxx" can be removed from the extension list.
"xxx" is listed multiple times.
"Object" should not be explicitly extended.
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]