Re-connect Stream Source when attribute change #1287
Draft
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.
Related to hotwired/turbo-rails#638
Recent changes to integrate with morphing have altered the mental model for some Turbo custom elements, including the
<turbo-stream-source>
element.Custom Elements'
connectedCallback()
anddisconnectedCallback()
(along with Stimulus'connect()
anddisconnect()
) improved upon invoking code immediately, or listening forDOMContentLoaded
events.There are similar improvements to be made to integrate with morphing. First, observe attribute changes by declaring their own
static observedAttributes
properties along withattributeChangedCallback(name, oldValue, newValue)
callbacks. Those callbacks execute the same initialization code as their currentconnectedCallback()
anddisconnectedCallback()
methods.That'll help resolve this issue. In addition to those changes, it's important to emphasize this pattern for consumer applications moving forward. JavaScript code (whether Stimulus controller or otherwise) should be implemented in a way that' resilient to both asynchronous connection and disconnection as well as asynchronous modification of attributes.