eva 1.2.0
eva: ^1.2.0 copied to clipboard
Event Architecture - A multithread event driven clean architecture framework
1.0.0 #
- Initial release
1.0.0+1 #
-
Some documentation fixes
-
Changed the license from GPL3 to BSD3, because people were worried they could not build a closed-source/commercial product with this framework. Now it is clear: YES, YOU CAN. =)
1.0.0+2 #
- The example to-do application is now explained step-by-step in README.md. Documentation by example.
1.0.0+3 #
- Fixed dependencies and some typos in the documentation
1.0.0+4 #
- Removed unused dependencies
1.0.0+5 #
- Update architecture graphic
1.0.1 #
- Changed the internal class
DomaintoDomainIsolateControllerto avoid confusion about what a domain class must extend (which is nothing, it must IMPLEMENT IDomain)
1.0.2 #
- Handling and executing
BackgroundIsolateBinaryMessenger.ensureInitialized()automatically in the background isolate
1.0.3 #
- Changing the
DomainIsolateController.dispatchEventto be non-protected, so repositories can dispatch events without a related command
1.1.0 #
- Due to incompatibilities with Firebase, now it is possible to completely turn off multithreading (maybe in the future Flutter will allow 2-way binary communication between platform and isolates)
- Now both
IDomainandIRepositoryare not immutable by default (because those places are perfect to store mutable states in your app) - Both
IDomainandIRepositoryno longer implementIInitializable, so they will NOT runvoid initialize()during their first use
1.1.0+1 #
- Documentation updates on optional multithreading
1.1.0+2 #
- Minor fix in multithreading
1.1.0+3 #
- Minor fix when multithreading = false
1.2.0 #
-
Now
successBuilderofEventBuilderis optional (but required ifotherwiseBuilderis not informed) -
BREAKING CHANGE:
EventBuilder<T>.initialValuenow must be anEvent<T>, so we can set an initial value of an empty value (i.e.:initialValue: const Event<Class>.empty()). Also,initialValueis only displayed while theStreamBuilderis waiting for the stream (otherwise, it will default toEvent<T>.waiting())