Phoenix Liveview using livecomponents for everything

[trisolaran]

@sergio

I remember reading in the docs somewhere that it’s recommended you create components as functions, and not as their own modules.

@llama

I tend to have separate modules for “main” components and then smaller components either grouped under those main component modules or into their own logical modules, such as buttons.ex, if they are used all over the place. I don’t know if it’s best practice, but it seems to work.

The OP is talking about live components, not function components. Each live component is its own module, and they can’t be grouped into a module.

@gXuEubhxAgHEd

My question: Is this good practice?? Is there anything livecomponents lose in comparison to being directly on the liveviews?

live components can’t react to changes in URL parameters (they don’t implement the handle_params/3 callback) and can’t receive messages via handle_info/2. However you can use attach_hook/4 to get around these limitations.