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

Blokh
Hey guys, I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly Do you guys have any suggestions what is the best prac...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
Onor.io
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
jaybe78
Hello, I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter). The diffic...
New
Trolleger
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
matt-savvy
Anyone here using Honeybadger? My Honeybadger account is being overwhelmed with noise from some bots. Seeing a lot of Bandit.HTTPError...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New

Other Trending Topics Top

garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
wintermeyer
There are three potential reasons for members of this forum to have a look at https://vutuv.de You are tired or annoyed of LinkedIn. Yo...
New
webofbits
Aludel - LLM Evaluation Workbench Aludel is an embeddable Phoenix LiveView dashboard for evaluating and comparing LLM prompts across mult...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews