You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+3-11Lines changed: 3 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ When performing a code review, ensure ViewModels are never injected as dependenc
8
8
9
9
When performing a code review, verify that all async operations use `viewModelScope.launch` instead of `GlobalScope.launch` in ViewModels.
10
10
11
-
When performing a code review, ensure Repository pattern is followed with proper data source abstraction.
11
+
When performing a code review, ensure Repository pattern is followed
12
12
13
13
When performing a code review, verify StateFlow is used for reactive state management in ViewModels with proper `_uiState` and `uiState` pattern.
14
14
@@ -18,10 +18,6 @@ When performing a code review, flag any use of the not-null assertion operator (
18
18
19
19
When performing a code review, ensure all coroutine operations use proper error handling with `runCatching`
20
20
21
-
When performing a code review, verify that all Logger calls include the TAG as context parameter, e.g., `Logger.warn("message", e = e, context = TAG)`.
22
-
23
-
When performing a code review, check that methods exist before they are called, especially after refactoring.
24
-
25
21
## UI & Compose Best Practices
26
22
27
23
When performing a code review, ensure all user-facing strings use `stringResource(R.string.*)` instead of hardcoded strings.
@@ -34,7 +30,7 @@ When performing a code review, ensure proper state management patterns with `Mut
34
30
35
31
## Code Quality & Readability
36
32
37
-
When performing a code review, focus on readability and avoid nested ternary operators.
33
+
When performing a code review, focus on readability and avoid nested if-else, replacing with early return wherever possible.
38
34
39
35
When performing a code review, ensure unused code is removed after refactoring.
40
36
@@ -48,11 +44,7 @@ When performing a code review, ensure services contain business logic and don't
48
44
49
45
## Build & Testing
50
46
51
-
When performing a code review, ensure proper build variant usage (dev for regtest, tnet for testnet).
52
-
53
-
When performing a code review, verify that unit tests follow the pattern `./gradlew testDevDebugUnitTest --tests ClassName`.
54
-
55
-
When performing a code review, suggest Unit Test com composable components and business logic covering the most important cases
47
+
When performing a code review, suggest Unit Test for composable components and business logic covering the most important cases
0 commit comments