Use hooks instead of LiveComponents #2026
Merged
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.
When I built the tabs for the Device page, and then used a similar pattern for the Deployment page, I quickly learnt that LiveComponents have a lot of quicks which lead to confusing code and duplicated state between the parent and child component.
For example, LiveComponents can't subscribe to topic, listen for pubsub messages, or respond to timer events.
I recently discovered a better path forward which uses LiveView hooks : https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#attach_hook/4
I've created some reusable code for implementing the same pattern with the Deployment page, and the upcoming Org pages.