Architecture MVVM
- Views should never MAKE USE of a service directly.
- Views should only contain logic if necessary. If the logic is from UI only items then we do the least amount of required logic and pass the rest to the ViewModel.
- Views should ONLY render the state in its ViewModel.
- ViewModels for widgets that represent page views are bound to a single View only.
- ViewModels may be re-used if the UI requires the same functionality.
- ViewModels should not know about other ViewModels.
CLean Architecture
Project Structure
- /bindings
# Binding 类是使用依赖注入，解耦视图(view)和控制器(controller)的类，需要“绑定”到路由到状态管理器和依赖管理器。
# 命名规则：$page_binding.dart
- /config
# App的配置文件，主要是一些常量
- controllers
# 控制器，处理业务逻辑
# logic bussiness code must be here.
- /data
# 所有跟数据相关的类，包括数据模型、数据存储、网络服务等
# Directory responsible for containing everything related to our data
- /helpers
# 一些帮助工具
- /models
# 数据模型（实体类）
# Our classes, or data models responsible for abstracting our objects.
- /provider
# 数据存储相关，可以是网络、本地数据库，
# 这是我们存储服务的地方
# 存储库只用来调解控制器和数据之间的通信。
# 控制器不需要知道数据来自哪里，如果需要，可以在一个控制器上使用多个存储库。
# 存储库必须由实体分隔，最好基于它们的数据库表。
# 并且在它内部将包含所有从本地 api 或数据库请求数据的函数。
# 也就是说，比如有一个用户表，增删改查这些接口都应该实现
# 从一个 api，我们将有一个包含这个 api 对象的存储库，我们将在其中调用所有相应的
# 对用户的功能。所以控制器不需要知道它来自哪里，存储库
# This is where we store our Services
# Here our repositories are just classes that will mediate the communication between our controller and our data.
# Our controllers won't need to know where the data comes from, and you can use more than one repository on a controller if you need to.
# The repositories must be separated by entities, and can almost always be based on their database tables.
# And inside it will contain all its functions that will request data from a local api or database.
# That is, if we have a user table that we will persist as, edit, add, update and delete, all these functions are requested
# from an api, we will have a repository with this object of the api where we will call all the respective
# functions to the user. So the controller does not need to know where it comes from, the repository being a
# mandatory attribute for the controllers in this model, you should always initialize the controller with at - /repository
- api_provider.dart
- db_provider.dart
- storage_provider.dart
- repository.dart
# Our data provider, can be an api, local database or firebase for example.
- /services
- dependency_injection.dart
# 依赖注入，需要全局注入的类
- service.dart
- /global_widgets
# Widgets that can be reused by multiple **modules**.
- /routes
# 路由
# In this repository we will deposit our routes and pages.
# We chose to separate into two files, and two classes, one being routes.dart, containing its constant routes and the other for routing.
- routes.dart
# class Routes {
# This file will contain your constants ex:
# class Routes { const HOME = '/ home'; }
- pages.dart
# This file will contain your array routing ex :
# class AppPages { static final pages = [
# GetPage(name: Routes.HOME, page:()=> HomePage())
# ]};
- /ui
- /demo
#存放一些demo的示例代码
- /global_widgets
#全局组件
- /layouts
#非全局用到的组件、布局
- /pages
#页面
- /values
- strings.dart
- colors.dart
- /languages
- /from
- pt-br.dart
- en-au.dart
- /theme
#主题
#Here we can create themes for our widgets, texts and colors
- text_theme.dart
# inside ex: final textTitle = TextStyle(fontSize: 30)
- color_theme.dart
# inside ex: final colorCard = Color(0xffEDEDEE)
- app_theme.dart
# inside ex: final textTheme = TextTheme(headline1: TextStyle(color: colorCard))
- /utils
#工具类
#Here you can insert utilities for your application, such as masks, form keys or widgets
- keys.dart
# inside ex: static final GlobalKey formKey = GlobalKey<FormState>();
- masks.dart
# inside ex: static final maskCPF = MaskTextInputFormatter(mask: "###.###.###-##", filter: {"#": RegExp(r'[0-9]')});
- helpers.dart
- extension_x.dart
# Use classes to make your variables easier to use, eg Keys.myKey, Masks.maskCPF
Library
- getx
- getx_pattern
- getx_cli #need vpn,like v2rayN、clash
- flutter_screenutil
- Lints
转载请注明来源，欢迎对文章中的引用来源进行考证，欢迎指出任何有错误或不够清晰的表达。可以在下面评论区评论，也可以邮件至 chgocn@gmail.com