Skip to content

feat: add good practices #4

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

Merged
merged 1 commit into from
Apr 19, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions flutter/good-practices.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
- structure your project by components
- use secure configuration with environment variables - flavors [flutter_flavorizr](https://pub.dev/packages/flutter_flavorizr)
- properly separate dependencies between 'dependencies' and 'dev_dependencies' in pubspec.yaml
- stick to the principles of DRY and KISS
- use unit tests for critical logic
- use [dio](https://pub.dev/packages/dio) for https calls
- use [get](https://pub.dev/packages/get). It combines high-performance state management, intelligent dependency injection, and route management quickly and practically.
- use [bot_toast](https://pub.dev/packages/bot_toast) flutter toast!
- use [shared_preferences](https://pub.dev/packages/shared_preferences) for localstorage
- use [lint](https://pub.dev/packages/lint) for liniting your code
- use [import_sorter](https://pub.dev/packages/import_sorter) for sort your imports in project
- if you need local db in your project use [hive](https://pub.dev/packages/hive)
- use [mockito](https://pub.dev/packages/mockito) for mocking data for your unit tests
- use [json_serializable](https://pub.dev/packages/json_serializable) for generating to/from JSON code for a class