empire 0.9.0 empire: ^0.9.0 copied to clipboard
A simple yet powerful state management library for Flutter. Keeps your widget build methods clean, with ZERO dependencies on other packages.
0.9.0 #
- Added
increment
anddecrement
functions to theEmpireIntProperty
- Updated the example project
- Updated README to reflect the property initialization refactor changes
- Added many factory constructors to various Empire Properties. (eg) EmpireDateTimeProperty.now() to create a DateTime property defaulted to the current Date/Time
BREAKING CHANGES
- We've redesigned and refactored how you go about initializing an EmpireProperty, and made it more dart-ly (it's a word now).
- Empire Properties in an EmpireViewModel are no longer initialized via a initProperties function that previously needed to be overridden, and was called by the ViewModel constructor behind the scenes. You can now instantiate a property as you would any other Dart object; via it's own constructor.
- There is a new getter List property called
empireProps
that must be overridden in a ViewModel. This should return the Empire Properties that you want to be reactive. (eg) Update the UI on change. - This change also allowed us to remove the requirement that all Empire Properties be defined with the late keyword.
- This change also allows consumers to inject Empire Properties into the ViewModel.
- Reorganized the library exports
In general, we will avoid major breaking changes if at all possible. In this case, as we approach a stable 1.0.0 release, we felt it was an overall improvement to the library based on valuable user feedback.
0.9.0-dev.3 #
- Changed
props
toempireProps
onEmpireViewModel
to prevent naming clashes with other popular packages (eg) Equatable - Added better exception handling/messaging if you forget to add a property to the
empireProps
list and try to update the property value.
0.9.0-dev.2 #
- Fixed issue where EmpireIntProperty
increment
anddecrement
functions were not updating the UI - Updated README to reflect the property initialization refactor changes
0.9.0-dev.1 #
- Added
increment
anddecrement
functions to theEmpireIntProperty
BREAKING CHANGES
-
We've redesigned and refactored how you go about initializing an EmpireProperty, and made it more dart-ly(it's a word now).
-
Empire Properties in an EmpireViewModel are no longer initialized via a initProperties function that previously needed to be overridden, and was called by the ViewModel constructor behind the scenes. You can now instantiate a property as you would any other Dart object; via it's own constructor.
-
This change also allowed us to remove the requirement that all Empire Properties be defined with the late keyword.
-
This change also allows consumers to inject Empire Properties into the ViewModel.
-
There is a new getter List property called props that must be overridden in a ViewModel. This should return the Empire Properties that you want to be reactive. (eg) Update the UI on change.
-
We've also added many factory constructors to various Empire Properties. (eg) EmpireDateTimeProperty.now() to create a DateTime property defaulted to the current Date/Time
-
Reorganized the library exports
-
Updated the example project
0.8.3 #
- Update package description to make Pub analysis happy
0.8.2 #
- Various code formatting and file structure clean up
- Updated example README
0.8.1 #
- CI Workflow Updates
- Documentation Generation Changes
0.8.0 #
- Initial library launch