That state prop passed into a Block instance is often stale or behind the real state, and props.editor.getState() is the preferred method for transforming state from within a block. Having state as its own prop seems overkill and a trap for the unsuspecting, I think the best way to fix this is just remove the prop!
Is there a use case for having state as it's own prop?
That
state
prop passed into a Block instance is often stale or behind the real state, andprops.editor.getState()
is the preferred method for transforming state from within a block. Havingstate
as its own prop seems overkill and a trap for the unsuspecting, I think the best way to fix this is just remove the prop!Is there a use case for having
state
as it's own prop?Steps to reproduce: