- updated to rxdart 0.25.0
- fixed iOS build settings in example project
- documentation fixes and small improvements by @AlexBacich thanks a lot!!!
- Fhttps://github.com/fluttercommunity/issues/44
-
PR by @AlexBacich and @nosmirck with a lot of little fixes
-
Updated dependency to rxdart
- Added helpful factory constructors to CommandResult
- Removed Flutter dependency
- Adapted to rxdart ^0.23.1 by abandoning Observables and use the new extension methods
-
Fix for fluttercommunity#32
-
Fix for fluttercommunity#33
- fix for fluttercommunity#26
If you encounter any problems please file an issue.
- PR with spelling corrections
- updated logo in readme
- Version bump to rxdart: ^0.22.0
- Bug fix in RxCommandListener
- Adding
next
property:
/// This property is a utility which allows us to chain RxCommands together.
Future<TResult> get next => Observable.merge([this, this.thrownExceptions.cast<TResult>()]).take(1).last;
- Thrown exceptions that are no descendants of the type Exceptions are no longer wrapped in an Exception object
- bugfix: If you created a command with
RxCommand.createFromStream
the isExecuting state was not set correctly
- bugfix fluttercommunity#9
- added RxCommandListener
- removed dependency to json_annotations
- Updated to rxdart v 0.19.0
- BREAKING CHANGE All creation functions got renamed to be more descriptive than the numbered ones. The new variants are:
static RxCommand<TParam, TResult> createSync<TParam, TResult>(Func1<TParam, TResult> func,...
static RxCommand<void, TResult> createSyncNoParam<TResult>(Func<TResult> func,...
static RxCommand<TParam, void> createSyncNoResult<TParam>(Action1<TParam> action,...
static RxCommand<void, void> createSyncNoParamNoResult(Action action,...
static RxCommand<TParam, TResult> createAsync<TParam, TResult>(AsyncFunc1<TParam, TResult> func,...
static RxCommand<void, TResult> createAsyncNoParam<TResult>(AsyncFunc<TResult> func,...
static RxCommand<TParam, void> createAsyncNoResult<TParam>(AsyncAction1<TParam> action,...
static RxCommand<void, void> createAsyncNoParamNoResult(AsyncAction action,...
- IMPORTANT: As of V3.0
CommandResult
objects are now emitted on the.results
property and the pure results of the wrapped function on the RxCommand itself. So I switched the two because while working on RxVMS it turned out that I use the pure result much more often. Also the name of.results
matches much better withCommandResult
. If you don't want to change your code you can just stay on 2.06 if you don't need any of V 3.0 features. - Also you now can set an
initialLastResult
when creating an RxCommand.
- Moved package to Flutter Community
- Fixed
quiver_hashcode
dependency issue.
- Update to RxDart 0.18.0
- Bug fix.
createAsync
andcreateAsync1
were missing an await.
- Till now the
results
Observable and theRxCommand
itself behaved like aBehaviourSubjects
. This can lead to problems when using with Flutter. From now on the default isPublishSubject
. If you needBehaviourSubject
behaviour, meaning every new listener gets the last received value, you can setemitsLastValueToNewSubscriptions = true
when creatingRxCommand
.
- Updated to accommodate a a breaking API change in RxDart 0.16.7 because no longer do Subjects expose an
observable
property because Subjects now implement Observable interface directly like other Rx implementation.
- Added an
emitLastResult
parameter to RxCommand factory functions. If true the last result will be transmitted in the data field ofCommandResults
whileisExecuting==true
orhasError==true
.
- RxCommand no longer issues an initial
CommandResult(null,null,false)
unless you setemitInitialCommandResult: true
when creating the command.
- Forgot to run tests and missed an error that I introduced following an analyser hint that I should use
const
instead ofnew
- Polishing and including
analysis_options.yaml
- Improvements and docs for MockCommand
- Added MockCommand
- RxCommands created by RxCommand.createFromStream no longer emit a final event after the last item of the source stream was received
- Added CommandResult, now RxCommand is itself an Observable that emits CommandResults
- Small update in docs
- Made RxCommand a callable class so that you now can directly assign it to your widget handlers
- Trying to fix the documentation link
- Removed the necessity of type
Unit
. Instead nowNull
is used
- Initial release.