-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coding Standard #42
Comments
This does not need to be strictly enforced for now, because we are in a rush, however keep this thing in mind |
For maintainability I have to do a code review from develop to master merge |
Are you aware of this @MouseAndKeyboard ? |
For now, no action will be taken except being aware that this exist. In stage 2, we have to go through all the files and reorder this |
I think one thing that this also needs are the ground rules that we set |
Only seen this now. |
@MouseAndKeyboard see changes |
I think there is something more with this issue aside from the imports... also the name of the component... I remember I had a bad practice to copy paste certain things from one components to another that I forgot to rename the function (didn't really matter as much in terms of functionality because of |
Import Order
it is important to have an order of import for code readability
I propose the order with alphabetical order enforced:
Frontend
Eg.
Backend ?? (not yet sure):
Note: Each number list will be separated by a space on import
The text was updated successfully, but these errors were encountered: