Stream runner in component

[johanfforsberg]

The ComponentSocket doesn't have a stream_runner method. I think it would be very useful for subscription type things on the component level. Am I missing something? Or are there technical reasons this can't be supported?

[ogrodnek]

You're right it's not currently available for components.

The stream_runner is a pyview thing that's implemented as handle_info events.

handle_info is not something that is implemented in Phoenix LiveView for components: https://hexdocs.pm/phoenix_live_view/Phoenix.LiveComponent.html#module-livecomponent-as-the-source-of-truth

However, note that components do not have a Phoenix.LiveView.handle_info/2 callback. Therefore, if you want to track distributed changes on a card, you must have the parent LiveView receive those events and redirect them to the appropriate card.

I'm guessing on the Phoenix side it's because components are part of the parent process and it also keeps the component model simpler.

So I didn't really think about it. I also knew that the current component implementation is somewhat basic/simple, but wanted to get it out there to get feedback on and iterate.

It does seem like a reasonable thing to add in pyview though, I think we could support it...

Thanks for the feedback! I'll keep this open and think about a potential implementation...