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: CONTRIBUTING.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,22 @@ TODO: Describe the branch structure, forking to a personal repository, pull requ
6
6
7
7
## Generated files
8
8
9
-
This project uses flutter freezed. Freezed files are not checked into git and must be generated locally using:
9
+
A `makefile` is available to assist you during the setup of the project and generate all needed files using the command `make setup`.
10
10
11
-
```
12
-
flutter pub run build_runner watch --delete-conflicting-outputs
13
-
```
11
+
12
+
## Guidelines
13
+
14
+
- Keep it simple.
15
+
16
+
- Write code that's easy to read and maintain think of your teammate who will read it next.
17
+
18
+
- Suffix your files (`_datasource.dart``_repository.dart``_model.dart``_usecase.dart``_entity.dart``_widget.dart``_page.dart` )
19
+
20
+
- Avoid creating unnecessary folders. Since most files have descriptive suffixes, only create a folder if you're placing multiple related files inside.
21
+
22
+
- Avoid abstract classes unless there's a clear current need. Don’t preemptively abstract for hypothetical future cases, start concrete, and refactor when it becomes necessary.
23
+
24
+
- Favor end-to-end and integration testing at the use case and widget level rather than relying on mocks. Since this is an app project, our priority is to catch real-world issues across layers. Mocking should be used only when necessary
0 commit comments