@@ -4,7 +4,7 @@ Great styling and naming schemes for classes, variables, objects, and methods is
...
@@ -4,7 +4,7 @@ Great styling and naming schemes for classes, variables, objects, and methods is
When the same thing is used in multiple places such as variables, methods, objects, use the same name. This helps readability between classes as you are clearly talking about a specific thing that is used there and nowhere else.
When the same thing is used in multiple places such as variables, methods, objects, use the same name. This helps readability between classes as you are clearly talking about a specific thing that is used there and nowhere else.
## Variable Guidelines
## Variable Guidelines
**Variables** must follow camelCase (including Ids, capital I, lowercase d). Examples: freshmenFunTimes, teacherId.
**Variables** must follow camelCase (IDs and DTOs are an exception). Examples: freshmenFunTimes, teacherID, questRecordDTOs.
Variables should **match** what they are in the database and in other classes if its the exact same thing.
Variables should **match** what they are in the database and in other classes if its the exact same thing.
...
@@ -28,4 +28,6 @@ Multiple similar objects, like DTOs, should have the consistently styled names,
...
@@ -28,4 +28,6 @@ Multiple similar objects, like DTOs, should have the consistently styled names,
In **GameServer** (The Back End, Java), **Class names** should be CamelCase with the first letter being capitalized.
In **GameServer** (The Back End, Java), **Class names** should be CamelCase with the first letter being capitalized.
DTO classes should have an underscore between the name and "DTO". For example, QuestRecord_DTO.
In **GameManager** (The Front End, DART), **Class names** should be snake_case.
In **GameManager** (The Front End, DART), **Class names** should be snake_case.
