Skip to content

Commit 8f18fc9

Browse files
Clarify package name style guide.
PiperOrigin-RevId: 868733437
1 parent a3b4949 commit 8f18fc9

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

content/programming-guides/style.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,14 +86,18 @@ rather than `XYZ_2` or `XYZ_2V`.
8686

8787
## Packages {#packages}
8888

89-
Use dot-delimited lower_snake_case names as package names.
89+
Packages names should be a dot-delimited sequence of lower_snake_case names.
90+
They should not contain uppercase letters.
9091

9192
Multi-word package names may be lower_snake_case or dot.delimited (dot-delimited
9293
package names are emitted as nested packages/namespaces in most languages).
9394

9495
Package names should attempt to be a short but unique name based on the project
95-
name. Package names should not be Java packages (`com.x.y`); instead use `x.y`
96-
as the package and use the `java_package` option as needed.
96+
name. The package should not be coupled with the directory path, especially when
97+
the files are in a deeply nested path.
98+
99+
Package names should not be Java packages (`com.company.x.y`); instead use `x.y`
100+
as the package and use the `java_package` option.
97101

98102
## Message Names {#message-names}
99103

0 commit comments

Comments
 (0)