Skip to content

Conversation

@is0sceles
Copy link
Contributor

You may wish to override areStatesEqual to always return false (areStatesEqual: () => false) if you have impure reducers that mutate your store state. (This would likely impact the other equality checks is well, depending on your mapStateToProps function.)

This paragraph's last line said 'is well'

You may wish to override areStatesEqual to always return false (areStatesEqual: () => false) if you have impure reducers that mutate your store state. (This would likely impact the other equality checks is well, depending on your mapStateToProps function.)

This paragraph's last line said "is well"
@timdorr
Copy link
Member

timdorr commented Jul 11, 2017

Thanks!

@timdorr timdorr merged commit 1a39f71 into reduxjs:master Jul 11, 2017
josepot pushed a commit to josepot/react-redux-lean that referenced this pull request Sep 21, 2018
You may wish to override areStatesEqual to always return false (areStatesEqual: () => false) if you have impure reducers that mutate your store state. (This would likely impact the other equality checks is well, depending on your mapStateToProps function.)

This paragraph's last line said "is well"
albertodev7 pushed a commit to albertodev7/react-redux that referenced this pull request Dec 8, 2022
You may wish to override areStatesEqual to always return false (areStatesEqual: () => false) if you have impure reducers that mutate your store state. (This would likely impact the other equality checks is well, depending on your mapStateToProps function.)

This paragraph's last line said "is well"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants