[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
247b2073f0fa7b77b08e8e8202030f555947fab9
Parent: ad9f467