/area frontend
Refactor Kale toolbar state polling to reactive state handling
During PR #611, polling (setInterval) was introduced in the Kale toolbar to monitor the Kale enabled state and update the Compile and Run button states accordingly.
While this works, polling is not ideal in a React-based application and does not align with a reactive state-driven architecture.
The implementation was intentionally kept minimal to avoid expanding the scope of that PR.
Proposed improvement
Refactor the toolbar state handling to use a reactive approach instead of time-based polling. The toolbar should update automatically when the Kale enable state changes, without relying on timers.
This may involve exposing the enable state via a callback, shared state mechanism, or a more reactive pattern within the labextension frontend.
This issue was discussed and agreed upon during PR #611.
Love this idea? Give it a 👍.
/area frontend
Refactor Kale toolbar state polling to reactive state handling
During PR #611, polling (
setInterval) was introduced in the Kale toolbar to monitor the Kale enabled state and update the Compile and Run button states accordingly.While this works, polling is not ideal in a React-based application and does not align with a reactive state-driven architecture.
The implementation was intentionally kept minimal to avoid expanding the scope of that PR.
Proposed improvement
Refactor the toolbar state handling to use a reactive approach instead of time-based polling. The toolbar should update automatically when the Kale enable state changes, without relying on timers.
This may involve exposing the enable state via a callback, shared state mechanism, or a more reactive pattern within the labextension frontend.
This issue was discussed and agreed upon during PR #611.
Love this idea? Give it a 👍.