Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/system-design/naming.md
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ Uservice user_service

在蛇形命名法中,各个单词之间通过下划线“\_”连接,比如`should_get_200_status_code_when_request_is_valid`、`CLIENT_CONNECT_SERVER_FAILURE`。

蛇形命名法的优势是命名所需要的单词比较多的时候,比如我把上面的命名通过小驼峰命名法给大家看一下:“shouldGet200StatusCodoWhenRequestIsValid”。
蛇形命名法的优势是命名所需要的单词比较多的时候,比如我把上面的命名通过小驼峰命名法给大家看一下:“shouldGet200StatusCodeWhenRequestIsValid”。

感觉如何? 相比于使用蛇形命名法(snake_case)来说是不是不那么易读?

Expand All @@ -128,7 +128,7 @@ void should_get_200_status_code_when_request_is_valid() {

```java
@Test
void shouldGet200StatusCodoWhenRequestIsValid() {
void shouldGet200StatusCodeWhenRequestIsValid() {
......
}
```
Expand Down