We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hi,first for you reductor share. we can subscribe the datas changes we can get notifiy. counterStore.subscribe(state -> System.out.println(state));
ok,it seems perfect,but when this happen .
there are Activity Named A,Activity Named B.
we start the A-->B
and we subscribe state in both A,B , at the same time ,A cares the datas field in state is a_name,a_sex and so on.
but B cares the datas field in state is b_name,b_sex, and so on.
when B send a dispatch action to change the b_name ,b_sex datas,
How Ever A had received the state callback the same ,i think this not very well .
in react -redux ,we use connect to diff the datas .
SO,the question is did't you had good methods to solve this problems?
The text was updated successfully, but these errors were encountered:
Is it possible to subscribe to changes in different parts of the AppState?
Sorry, something went wrong.
You can use Cursors.map method to subscribe the data you want
No branches or pull requests
hi,first for you reductor share. we can subscribe the datas changes we can get notifiy.
counterStore.subscribe(state -> System.out.println(state));
ok,it seems perfect,but when this happen .
there are Activity Named A,Activity Named B.
we start the A-->B
and we subscribe state in both A,B , at the same time ,A cares the datas field in state is a_name,a_sex and so on.
but B cares the datas field in state is b_name,b_sex, and so on.
when B send a dispatch action to change the b_name ,b_sex datas,
How Ever A had received the state callback the same ,i think this not very well .
in react -redux ,we use connect to diff the datas .
SO,the question is did't you had good methods to solve this problems?
The text was updated successfully, but these errors were encountered: