2023-05-03 11:06:20 +02:00
== Why is this an issue?
2023-06-08 08:03:28 +02:00
Shared naming conventions allow teams to collaborate efficiently.
2020-06-30 10:16:44 +02:00
2023-06-08 08:03:28 +02:00
This rule raises an issue when a struct name does not match a provided regular expression.
2021-02-02 15:02:10 +01:00
2023-06-08 08:03:28 +02:00
The convention in Go is to use mixedCaps rather than underscores. See https://golang.org/doc/effective_go.html#names[Go documentation] for the complete naming conventions.
2021-02-02 15:02:10 +01:00
2020-06-30 10:16:44 +02:00
Note that the casing of the first character determines if the type is exported or not.
2023-06-08 08:03:28 +02:00
For example, with the default provided regular expression ``++^[a-zA-Z][a-zA-Z0-9]*$++``, the struct:
2020-06-30 14:49:38 +02:00
2022-02-04 17:28:24 +01:00
[source,go]
2020-06-30 10:16:44 +02:00
----
type my_struct struct {...}
----
2023-06-08 08:03:28 +02:00
should be renamed
2020-06-30 10:16:44 +02:00
2022-02-04 17:28:24 +01:00
[source,go]
2020-06-30 10:16:44 +02:00
----
type myStruct struct {...}
----
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
2023-06-22 10:38:01 +02:00
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]