rspec/rules/S101/cfamily/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

64 lines
1001 B
Plaintext

== Why is this an issue?
Shared naming conventions allow teams to collaborate efficiently.
This rule raises an issue when a class name (or an Objective-C interface, protocol, or implementation name) does not match a provided regular expression.
For example, with the default provided regular expression ``++^[A-Z][a-zA-Z0-9]*$++``, the following class and interface:
[source,cpp]
----
// C++
class foo // Noncompliant
{
};
// Objective-C
@interface nonCompliant: NSObject
@end
----
should be renamed to
[source,cpp]
----
// C++
class Foo
{
};
// Objective-C
@interface Compliant: NSObject
@end
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
=== Parameters
.format
****
_STRING_
----
^[A-Z][a-zA-Z0-9]*$
----
Regular expression used to check the class names against.
****
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]