Anko

Anko

I have a bunch of components and a list of data with different “types”. I want to render the appropriate component depending on the type of the data.

This is basically the code i am trying, but i’m not sure the best way to do it with heex.

    for {agg, results} <- @data_list do
      case agg.type do
        "price_stats" -> ~H"""
          <.live_component module={ComponentTestWeb.Components.StatsFacet} id={agg.internal_name} title={agg.title} items={results} />
        """
        _ -> ~H"<.live_component module={ComponentTestWeb.Components.KeywordFacet} id={agg.internal_name} title={agg.title} items={results} />"
      end
    end

How should I do this? I have tried it in the template, but i couldn’t find a good example of case statements in the template. So then i thought i’d do it as a functional component, but it’s not clear to me how to set the assigns correctly. For example, this says i’m doing the wrong thing for change tracking;

  def show_facets(assigns) do
    
    for {agg, results} <- assigns.agg_results do
      case agg.type do
        "price_stats" -> ~H"""
          <.live_component module={ComponentTestWeb.Components.StatsFacet} id={agg.internal_name} title={agg.title} items={results} />
        """
        _ -> ~H"<.live_component module={ComponentTestWeb.Components.KeywordFacet} id={agg.internal_name} title={agg.title} items={results} />"
      end
    end
  end

Showing Posts 1 to 3

kokolegorille

kokolegorille

Maybe like this (not tested)

alias ComponentTestWeb.Components.{StatsFacet, KeywordFacet}
def show_facets(assigns) do
  for {agg, results} <- assigns.agg_results do
    show_agg(agg, results)
  end
end

defp show_agg(%{type: "price_stats"} = agg, results) do
  assigns = %{agg: agg, results: results}
  ~H"""
    <.live_component module={StatsFacet} id={@agg.internal_name} title={@agg.title} items={@results} />
  """
end
defp show_agg(agg, results) do
  assigns = %{agg: agg, results: results}
  ~H"""
    <.live_component module={KeywordFacet} id={@agg.internal_name} title={@agg.title} items={@results} />
  """
end
sodapopcan

sodapopcan

I would do something like this (also untested):

alias ComponentTestWeb.Components.{StatsFacet, KeywordFacet}

def facets(assigns) do
  ~H"""
  <%= for {agg, result} <- @agg_results do %>
    <.agg_result agg={agg} result={result} />
  <% end %>
  """
end

defp agg_result(%{agg: %{type: "price_stats"}} = assigns) do
  ~H"""
  <.live_component module={StatsFacet} id={@agg.internal_name} title={@agg.title} items={@results} />
  """
end

defp agg_result(assigns) do
  ~H"""
  <.live_component module={KeywordFacet} id={@agg.internal_name} title={@agg.title} items={@results}
  """
end
LostKobrakai

LostKobrakai

I’d just put this 1:1 into heex and be fine. No need to make this more complicated unless it becomes unwieldy.

~H"""
<%= for {agg, results} <- @data_list do %>
  <%= case agg.type do %>
    <% "price_stats" -> %>
      <.live_component module={ComponentTestWeb.Components.StatsFacet} id={agg.internal_name} title={agg.title} items={results} />
    <% _ -> %>
      <.live_component module={ComponentTestWeb.Components.KeywordFacet} id={agg.internal_name} title={agg.title} items={results} />
  <% end %>
<% end %>
"""

If it’s however only the module changing you can also do this:

~H"""
<%= for {agg, results} <- @data_list do %>
    <.live_component module={component_by_type(agg.type)} id={agg.internal_name} title={agg.title} items={results} />
<% end %>
"""

defp component_by_type("price_stats"), do: ComponentTestWeb.Components.StatsFacet
defp component_by_type(_), do: ComponentTestWeb.Components.KeywordFacet
10
Post #3
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
apz
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New

Other Trending Topics Top

GenericJam
Edit: 2026 May 15 - This post is archived. Mob is alive!! Main docs: mob v0.7.11 — Documentation A bit of explanation for the slightly c...
New
JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews