[React] Add permanent
option to react_component
function
#2283
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Issue reported on a work project)
Using Turbo
data-turbo-permanent
creates race conditions that lead to the controller code failing to keep or reload the component.In the current implementation, the Stimulus controller unmounts the component then tried to create it again.. which cannot be done:
https://react.dev/reference/react-dom/client/createRoot#root-unmount
The proposed implementation uses a short delay before calling unmount. It is "morphing-library-agnostic", and will work with any Turbo-like framework, with no impact on the existing projects using UX React (except a bug fixed 😅 ).New implementation:
A new option
permanent
prevent the "unmount" of the component when set to trueThis allows to avoid the bug when a component is disconnected and immediately reconnected (ex with Turbo)