The purpose is to learn best practices, write tests, and use Flutter for Web on production.
- We will be using classic git-flow. No one has to fork to the project. Everyone who has access to the project can and should clone it.
- The direct merge to the main branch is forbidden. All the code should go through the code review process.]
- Write on any issue you want to work on.
- Clarify the details
- Then, do the implementation.
Please use the following template for branch creation
For features:
feature/FTW-(issue-Number)-(name-of-the-feature)
bugfix/FTW-(issue-Number)-(name-of-the-bugfix)
The template to the pull request will be updated with some points, but until then please:
- Create the pull request with a screenshot of what you developed
- Put the assignee until CODEOWNERS is there
StatefulWidget approach will be the approach to follow.
As a rule of thumb, try to follow the Dart analyzer and follow the rules.
- DO use new class widgets / DON'T use functions for widgets
- ...
Flutter 2.10.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 7e9793dee1 • 2022-03-02 11:23:12 -0600
Engine • revision bd539267b4
Tools • Dart 2.16.1 • DevTools 2.9.2
