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
Codephile is an application specially made for all the competitive coders out there. With features
4
-
like submission feed, contest reminders, user search, and many more, this app is a perfect companion
5
-
for stalking your fellow coders and learning from them.
3
+
Codephile is an application specially made for all the competitive coders out there. With features like submission feed, contest reminders, user search, and many more, this app is a perfect companion for stalking your fellow coders and learning from them.
6
4
7
5
## Screenshots
8
6
@@ -14,42 +12,76 @@ for stalking your fellow coders and learning from them.
14
12
Project structure:-
15
13
16
14
```
17
-
|-lib
18
-
| |-models {contains object models | used for communication with the back-end}
19
-
| |-screens {contains code for the UI}
20
-
| |-services {contains code for the buisness logic}
21
-
| |-resources {common resources like assets addresses}
Some of the code in this app is generate by pub tools.
52
+
53
+
```
54
+
$ flutter pub run build_runner build --delete-conflicting-outputs
55
+
```
56
+
57
+
#### 3. Run the app
58
+
59
+
We've added two `.idea` and `.vscode` folders to help you run the app in your IDE of choice. If those aren't working properly, use the following command.
60
+
61
+
```
62
+
$ flutter build apk --flavor development --target lib/main_development.dart
27
63
```
28
64
29
65
## How to Contribute
30
66
31
67
We'd love to accept your patches and contributions to this project. There are just a few small
32
68
guidelines you need to follow.
33
69
34
-
- When contributing to this repository, please first discuss the change you wish to make via the
35
-
issues section before starting any major work.
36
-
- Once you have started work on any issue open a WIP pull request addressing that issue so that we
37
-
know that someone is working on it.
38
-
- While writing any code for this project ensure that it is well formatted and consistent with the
39
-
architecture of the rest of the project.
40
-
- Please make sure that you use the
41
-
standard [dart nomenclature](https://dart.dev/guides/language/effective-dart/style).
70
+
- When contributing to this repository, please first discuss the change you wish to make via the issues section before starting any major work.
71
+
- Once you have started work on any issue open a WIP pull request addressing that issue so that we know that someone is working on it.
72
+
- While writing any code for this project ensure that it is well formatted and consistent with the architecture of the rest of the project.
73
+
- Please make sure that you use the standard [dart nomenclature](https://dart.dev/guides/language/effective-dart/style).
42
74
- Before committing any change make sure their is no compilation warning or error.
43
75
44
-
### For commit messages
76
+
##Commit messages
45
77
46
-
Please start your commits with these prefixes for better understanding among collaborators, based on
47
-
the type of commit:
78
+
Please start your commits with these prefixes for better understanding among collaborators, based on the type of commit:
48
79
49
-
feat: (addition of a new feature)
50
-
rfac: (refactoring the code: optimization/ different logic of existing code - output doesn't change, just the way of execution changes)
51
-
docs: (documenting the code, be it readme, or extra comments)
52
-
bfix: (bug fixing)
53
-
chor: (chore - beautifying code, indents, spaces, camelcasing, changing variable names to have an appropriate meaning)
54
-
ptch: (patches - small changes in code, mainly UI, for example color of a button, incrasing size of tet, etc etc)
0 commit comments