Check for store changes before firing.changed

[OverHash]

This PR closes #32

However, more discussion needs to be done around this (e.g. this is quite a costly operation, do we want to really run it by default? do we want to run it recursively)

[coveralls]

Coverage decreased (-0.5%) to 98.857% when pulling 1ed7417 on OverHash:master into efda50f on Roblox:master.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[ZoteTheMighty]

I think the reason that #32 suggests checking only the top-level store values is because reducers should always honor data immutability anyways. If any value changed anywhere in the store, a correctly built set of reducers will result in a change in one of the top-level state fields.

Going through this recursively feels like we're optimizing for an incorrect usage and paying a performance cost for it, so it doesn't sit well with me. I left a comment on #32 to this effect, but I think I'm unconvinced that this is even worth checking at all, even if we compare shallowly.

[OverHash]

Yep, I agree. Closing this PR.