Not bad, but you can't rely on this package in the long run. Quite interesting and promising features, for example, filtering of reactive events, were silently removed by the author of the package just six months ago. And I have not found the reasons for such refactoring anywhere in the descriptions. I looked at this package too, tested it and gave it up. Personally, I need more package stability.
From my experience, this package has been totally different with the original version 1 and the syntax might not consistent with flutter Bloc package. Personally, that's no right and wrong to keep something innovative and somebody like me always welcome to try something new.
In relation to the reactive event & filtering as you mentioned, I used to define a dependsOn into a inject state that can easily achieve global state to state communication (A hasData will trigger B). On the other, for filtering the rebuild by condition, just define shouldRebuild, all syntax looks clear and clean.
One of the downside of this package is the community is obviously not as popular as others and it's nice to see it keeps growing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Another great solution is States_rebuilder which should be added, it has a very nice syntax and a pure dart that supports immutable state management.
pub.dev/packages/states_rebuilder
Not bad, but you can't rely on this package in the long run. Quite interesting and promising features, for example, filtering of reactive events, were silently removed by the author of the package just six months ago. And I have not found the reasons for such refactoring anywhere in the descriptions. I looked at this package too, tested it and gave it up. Personally, I need more package stability.
From my experience, this package has been totally different with the original version 1 and the syntax might not consistent with flutter Bloc package. Personally, that's no right and wrong to keep something innovative and somebody like me always welcome to try something new.
In relation to the reactive event & filtering as you mentioned, I used to define a
dependsOn
into a inject state that can easily achieve global state to state communication (A hasData will trigger B). On the other, for filtering the rebuild by condition, just defineshouldRebuild
, all syntax looks clear and clean.One of the downside of this package is the community is obviously not as popular as others and it's nice to see it keeps growing.