One issue that I really had recurring here is that most of my Om components are just for rendering (their state doesn't change) but I often change their state on code while developing it and because the component state is retained I have to work around to get the new state there.
This request is a proposal for a new option called :static-state (please let me know if you have a better name). When you set that to true it will force the component state to be updated on the code reload, ensuring the latest state there without extra friction.
bhauman
commented
8 years ago
Hi,
One issue that I really had recurring here is that most of my Om components are just for rendering (their state doesn't change) but I often change their state on code while developing it and because the component state is retained I have to work around to get the new state there.
This request is a proposal for a new option called
:static-state(please let me know if you have a better name). When you set that to true it will force the component state to be updated on the code reload, ensuring the latest state there without extra friction.