Orientação gerada a partir de informações públicas. Apenas para referência.
HydratedTriple é um pacote Flutter/Dart que simplifica a gestão de estado ao persistir e restaurar automaticamente o estado do armazenamento entre reinicializações do aplicativo. Construído sobre o padrão Triple, integra-se perfeitamente com Riverpod ou Provider, permitindo que desenvolvedores mantenham dados do usuário como preferências, status de login ou entradas de formulários sem serialização manual. O mixin cuida da salvaguarda do estado no armazenamento local (por exemplo, SharedPreferences) e da rehidratação quando o aplicativo for iniciado, reduzindo o código repetitivo e melhorando a experiência do usuário. É ideal para aplicativos que exigem persistência confiável de estado com configuração mínima.
Casos de uso
Persistência de preferências do usuário
Restaurando o estado de login após reiniciar
Salvando dados do formulário temporariamente
Manter configurações do aplicativo entre sessões
Gerenciando cenários de primeiro offline
Principais recursos
Persistência automática de estado
Integração sem problemas com Riverpod/Provider
Suporta múltiplas plataformas
Boilerplate mínimo
Serialização embutida
Compatibilidade multiplataforma
Indicado para
Aplicativos que precisam de estado persistente
Desenvolvedores usando o padrão Triple
Projetos com funcionalidade off-line
Equipes que priorizam a produtividade do desenvolvedor
Gerenciamento de estado com código mínimo
Considerações
Requer serialização correta de objetos de estado
Pode aumentar levemente o tempo de inicialização do aplicativo
Não adequado para estado grande ou frequentemente alterado
Limitado a estruturas de estado simples, a menos que lógica personalizada seja adicionada
Depende da solução de gerenciamento de estado subjacente
README original
Snapshot do README original do repositório-fonte vinculado. Consulte o repositório para o conteúdo mais recente.
Triple - Segmented State Pattern
Welcome to Triple!
Design Pattern for State Management.
Triple is a nickname to SSP (Segmented State Standard).
Some packages were created to make it easier for developers to start using the standard. We'll call it an extension.
Segmented State Pattern (SSP)
When we talk about a single flow state, we end up solving architecture problems early, as we will have only one data flow for each state.
In addition to the maintainability and to the ease of use architecture, we also have the possibility of increasing this flow with other standards such as the Observer, which gives reactivity to the component when it is modified, and Memento, which makes it possible to revert or redo this state.
A beautiful example of a pattern with a single flow is BLoC, giving reactivity to a state allowing all transformations in that flow. This (although complicated for some), consolidates very well in the architecture of a project, even the limits of this practice are beneficial for not allowing the developer to resort to other solutions for the architecture and the standard for its resource.
There are other ways to promote reactivity in a property instead of the entire object, such as MobX's Observable and Flutter's ValueNotifier, and that gives us a lot of choices. However, we lose some important architecture limits, which can put in check the project maintenance in the future. Therefore, it needs a standard to force limits on the individual reactivity of each property and thereby improve the maintainability of the components responsible for managing the states of the application.
Triple is a nickname to SSP (Segmented State Standard). Some packages were created to make it easier for developers to start using the standard. We'll call it an extension.
This project is distributed under the MIT License. See LICENSE.txt for more information.
✨ Usage
The SSP segments the state into 3 reactive parts, the state value (state), the error object (error), and the state loading action (loading).
These segments are observed in a listener or separate listeners. They can also be combined to obtain a new segment, always starting from the 3 main segments.
Installation
Dependencies
add the following dependencies to your pubspec.yaml file:
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the appropriate tag.
Don't forget to give the project a star! Thanks again!
Fork the Project
Create your Feature Branch (git checkout -b feature/AmazingFeature)
Commit your Changes (git commit -m 'Add some AmazingFeature')
Push to the Branch (git push origin feature/AmazingFeature)