Skip to content

Commit eb7d0c7

Browse files
authored
Apply suggestions from code review
1 parent cf77e4a commit eb7d0c7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/resources/style-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ When naming custom data types and enums, use **UpperCamelCase** for consistency
9090
- **Don’t Mix Naming Conventions for Enums:** Maintain consistent capitalization between enum names and their values. Bad Example: `enum UserRole { Admin, EDITOR, viewer }`
9191
:::
9292

93-
For datatype fields, we use the same convention as [State variables](#state-variables).
93+
For datatype fields, we use the same convention as [State variables](#variables).
9494

9595
### Constants
9696

@@ -106,7 +106,7 @@ Flutter prefers using a lowercase `k` prefix for constants to indicate their imm
106106
- **Don’t Use Vague or Generic Names:** Avoid using names that fail to describe the purpose of the constant. Bad Examples: `VALUE`, `DATA`, `X`, `Y`.
107107
:::
108108

109-
### State Variables & Data Type Fields
109+
### Variables
110110

111111
State variable & Data Type field names follow the **lowerCamelCase** naming style to align with Dart's conventions.
112112

0 commit comments

Comments
 (0)