[compiler] Improve setState-in-effects rule to account for ref-gated conditionals
Conditionally calling setState in an effect is sometimes necessary, but should generally follow the pattern of using a "previous vaue" ref to manually compare and ensure that the setState is idempotent. See fixture for an example.
J
Joe Savona committed
a16bcf9a0073b10ba0e73e5b9ce4e0f419c68b14
Parent: 437cae2