fireproofsocks

fireproofsocks

I’m trying to build a loop in an EEx template that may have to iterate over a list OR a map (i.e. loop over its keys/values) and include an index (yes, I know that’s a lot).

So far, my EEx template looks like this:

The start...
<%= Enum.with_index(list)
|> Enum.map(fn {x, index} ->
    case x do
      {k, v} -> %>
        <%= k %> <%= v %>: @index: <%= index %>
    <% x -> %>
          <%= x %>: @index: <%= index %>
    <% end %>
<% end) %>
...The end.

But that results in an error:

** (TokenMissingError) nofile:12: missing terminator: end (for "fn" starting at line 3)
    lib/eex/compiler.ex:101: EEx.Compiler.generate_buffer/4
    lib/eex/compiler.ex:54: EEx.Compiler.generate_buffer/4
    lib/eex.ex:199: EEx.eval_string/3
    my_file.exs:37: (file)

A simpler EEx template works:

The start...
<%= Enum.with_index(list)
|> Enum.map(fn {x, index} -> %>
      <%= x %>: @index: <%= index %>
<% end) %>
...The end.

but that one only handles lists. I think I’m getting stuck on where exactly I’m allowed to break in and out of Elixir code within an EEx template. The basic logic works when it’s not in EEx.

Thanks for any pointers!

Showing Posts 1 to 6

patrickdm

patrickdm

Hello, I’d try to simplify it by moving the function to the view module, using string interpolation, i.e. (disclaimer: untested code ahead..)

def eval_item(x, index) do
  case x do
    {k, v} -> 
      "#{k} #{v} : @index: #{index}"
    val ->
      "#{val} : @index: #{index}"
    end
end

or with two functions using pattern matching on arguments (that I prefer as I find it easier to read):

def eval_item({k, v} = x, index), do: "#{k} #{v} : @index: #{index}"

def eval_item(x, index), do: "#{x} : @index: #{index}"

then in the template you could just:

<%= Enum.with_index(list) |> Enum.map(&eval_item/2) %> 

hth.

kokolegorille

kokolegorille

I would even go further and put all logic in a helper function. Putting logic in the template is not something I would advise.

Somehing like

<%= do_something(list) %> 
patrickdm

patrickdm

yes, good advice! :slight_smile:

[..edit..] Putting all together would look like:

in template.html.eex

<%= iterate_over(list) %> 

in template_view.ex

def iterate_over(list) do
 list
 |> Enum.with_index()
 |> Enum.map(&eval_item/2)
end

defp eval_item({k, v} = _x, index), do: "#{k} #{v} : @index: #{index}"

defp eval_item(x, index), do: "#{x} : @index: #{index}"
fireproofsocks

fireproofsocks OP

These are good suggestions, but I’m not sure how to implement these inside of a template where the user’s formatting string (i.e. the template itself) needs to be referenced in the function (rather than the hard-coded example strings like "#{k} #{v} : @index: #{index}"

I might have to go meditate a bit more at the altar of Enum…

fireproofsocks

fireproofsocks OP

I figured out a solution based on your suggestions… I just had to jiggle my EEx tags around. There was an important caveat I had to consider here that makes it a better solution to have this logic done in the template – it has to do with a Handlebars parser I’m writing: GitHub - fireproofsocks/zappa: Elixir implementation of the Handlebars template language · GitHub

In the below example, both the list or map input options work:

      input = ["apple", "boy", "cat"]
      input = %{x: "xray", y: "yellow"}
      eex = ~s"""
          <ul>
          <%= Enum.with_index(list) |> Enum.map(fn({x, index}) -> %>
              <%= if is_tuple(x) do %>
                <% {k, v} = x %>
                <li><%= k %>: <%= v %></li>
              <% else %>
                <% this = x %>
                <li><%= this %></li>
              <% end %>
            <%= end) %>
          </ul>
      """

      out = EEx.eval_string(eex, list: input)

Yes, that looks awful, but this structure will work in my weird use-case.

Ninigi

Ninigi

<% %> doesn’t work like that (been there tried that :slight_smile:), and you can simplify the map/case by pattern matching in the function signatures.

untested:

<%= Enum.with_index(list) |> Enum.map(fn
  {{k, v}, index} ->
    "#{k} #{v}: @index: #{index}"
  {x, index} ->
    "#{x}: @index: #{index}"
end) %>
— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
itzmidinesh
Hi all, I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
leoschweizer
Hi, we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
csmr
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley: Mutonex gamedesign was finish...
New
Stef-Verniers
Hello I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New

Other Trending Topics Top

dominicletz
Hey there, I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first. ...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
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
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New
OndrejValenta
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly) AI dream has many faces, but general...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews