Add lifecycle callbacks for components.#436
Merged
hayleigh-dot-dev merged 3 commits intomainfrom Feb 15, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces three new component options, two being usable in both server component and client components, and one being exclusively for client components:
component.on_connectcomponent.on_adoptcomponent.on_disconnectEach option sets a message that should be dispatched to the runtime at different points in the component's lifecycle. For client components these three options correspond to the custom element lifecycle callbacks
connectedCallback,adoptedCallback, anddisconnectedCallback.For server components
on_connectandon_disconnectcan be used to be notified when a new connection is registered or deregistered throughserver_component.register_subject/callbacketc.These lifecycle messages provide important hooks for components to launch effects or perform important cleanup, and addresses #320 without the need for explicit effect cleanup capabilities or a fixed shutdown/stop event.