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.
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
dependsOninto 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.