Updated content under Naming Conventions in api-conventiones.md
This commit is contained in:
parent
19b6ff012e
commit
c9ae4756d5
|
@ -1145,7 +1145,7 @@ reduce data volume, load on the system, and noise exposed to users.
|
||||||
|
|
||||||
## Naming conventions
|
## Naming conventions
|
||||||
|
|
||||||
* Go field names must be Pascal case. JSON field names must be camelCase. Other
|
* Go field names must be PascalCase. JSON field names must be camelCase. Other
|
||||||
than capitalization of the initial letter, the two should almost always match.
|
than capitalization of the initial letter, the two should almost always match.
|
||||||
No underscores or dashes in either.
|
No underscores or dashes in either.
|
||||||
* Field and resource names should be declarative, not imperative (SomethingDoer,
|
* Field and resource names should be declarative, not imperative (SomethingDoer,
|
||||||
|
|
Loading…
Reference in New Issue