Although this is a quick example, it shows the different roles function components play in Phoenix:
Function components can be defined as functions that receive assigns as argument and call the ~H sigil, as we did in greet/1
Function components can be embedded from template files, that’s how we load show.html.heex into HelloWeb.HelloHTML
Function components can declare which attributes are expected, which are validated at compilation time
Function components can be directly rendered from controllers
Function components can be directly rendered from other function components, as we called <.greet messenger={@messenger} /> from show.html.heex
Ask: How do I render a functional components (that is the function returning ~H sigil) directly from controller function without needing a .html.heex template in the middle? Couldn’t find any examples for it in docs
I think that may be just weird wording referring to how you can do this:
def MyAppWeb.FooController do
use MyAppWeb, :controller
def index(conn, _params) do
render(conn, :index)
end
end
def MyAppWeb.FooHTML do
use MyAppWeb, :html
def index(assigns) do
~H"""
My template
"""
end
end
def index(assigns) is a component which is rendered from the controller by referencing its name as opposed to “rendering a template from the controller.” AFAIK, you can’t render heex inside a controller action which is what you’re asking. If you have some better wording you could always open a PR to improve!
It’s possible I’m wrong and you can do what you’re asking but I’ve searched through the docs and can’t find anything. render doesn’t take HEEx at all.
@sodapopcan thanks, this is what I was looking for! The examples I came across render a .html.heex “template” rather than a component directly. But this answers "how to skip the .html.heex templates. I’ll send a PR to docs to add this example as well
@LostKobrakai that’s interesting! letting you skip the view layer (i,e, MyAppWeb.FooHTML) completely
