A solution to having more templates per component collocated with it in the same folder

That is great Does it work the same way for live view? Want to publish it as a small library on hex.pm?

Good question. Actually, never thought of using it in a live view for there’s a common pattern to rely on the Phoenix.View.render/2 function and I created this module because there there was no such functionality available for the LiveComponents.

But now that you mention it, I can try and see. If you have the time to try it first (with a live view), you’re more than welcome.

And if it does work there too or it requires minor modifications, yes, I could publish it as a small library.

Cool. Will try it later today or tomorrow.

Worked in live view like a charm!

That’s great. Now the only thing remaining prior to releasing it as a library is to figure out a proper name for the module, given its generic application for both the live components and live views and the fact that it extends the standard functionalities of LiveView.

Is there any prescribed LiveView extension naming convention? E.g. Phoenix.LiveView.Renderer.Helpers, or to avoid confusing the library name with the official LiveView releases, something like: Extensions.LiveView.Renderer ?

What do the LiveView authors have to say @josevalim? Any suggestions given the fact that a good part of the code in this small library to be was taken from the Phoenix.LiveView.Renderer module?

Any name is fine as long as you don’t step into Phoenix or LiveView namespaces, as to avoid conflicts in the future. For example, do: PhoenixLiveViewWhatever, don’t do Phoenix.LiveViewWhatever or Phoenix.LiveView.Whatever.

So, Extensions.LiveView.Renderer is ok, right?

If your package is called extensions, yes. If you want something more concrete: one suggestion is PhoenixLiveViewMultiRender

Thanks, Jose. I like the MultiRender name, but will stick to the idea of the Extensions top-package as there may be more of those on my behalf over time and I dislike too long camelized names for they remind me of Java which was cool back in 1998, but Elixir and everything about it is so much paradigmatically superior that I have no desire to get reminded of the former.
Therefore: Extensions.LiveView.MultiRender

Just want to highlight that installing your library would look something like this:

{:extensions, "~> 1.0.0"}

A bit confusing if you’d ask me. I’m more for clear names, where it’s obvious what the library is for. Also it will be easier to find it on hex.pm.

{:phoenix_live_view_multi_renderer, "~> 1.0.0"}
{:live_view_multi_renderer, "~> 1.0.0"}
{:lv_multi_renderer, "~> 1.0.0"}
{:multi_renderer, "~> 1.0.0"}