martijn

martijn

In my first Phoenix app, I have an action which serves an XML phonebook to a certain SIP handset. The handset has two ways of calling this action:

/gigaset?reqsrc=user&ln=foo   # Search for a contact with the name 'foo'
/gigaset?reqsrc=auto&hm=12345 # Search for a contact with caller ID 12345

Since both have different queries I decided to pattern match based on the reqsrc parameter. But both action have some shared logic as well, so I put that in a separate method with the same name but different arity to apply limit and offset and render the view/template. It works, but is this the right way of doing things?

  # User quering phonebook from Gigaset base
  def gigaset(conn, params = %{"reqsrc" => "user"}) do
    name = String.replace(params["ln"], "*", "%")
    query = from e in Entry, where: ilike(e.name, ^name)

    gigaset conn, query, params
  end

  # Caller ID from Gigaset base
  def gigaset(conn, params = %{"reqsrc" => "auto"}) do
    number = params["hm"]
    query = from e in Entry, where: e.work == ^number or e.home == ^number or e.mobile == ^number

    gigaset conn, query
  end

  # Finish query, render output
  def gigaset(conn, query, params) do
    limit = String.to_integer(params["count"])
    offset = String.to_integer(params["first"]) - 1

    query = from e in query, limit: ^limit, offset: ^offset
    entries = Repo.all(query)

    render conn, entries: entries
  end

I know the difference in the query is trivial, but imagine they would be vastly different. Does it make sense to do it like this?

Showing Posts 1 to 3

martijn

martijn OP

Wait.. after testing it again it seems to not work as expected :persevere:

Requesting /gigaset?reqsrc=auto yields a ‘no matching action clause to process request’ error on the definition of the first method. Is there a way to do this, at all?

I ended up rewriting into this long method (with some more changes):

  def gigaset(conn, params = %{ "reqsrc" => reqsrc, "count" => limit, "first" => offset }) do
    query = case reqsrc do
      # User quering phonebook from Gigaset base
      "user" ->
        name = String.replace(params["ln"], "*", "%")
        from e in Entry, where: ilike(e.name, ^name)

      # Caller ID from Gigaset base
      "auto" ->
        number = params["hm"]
        from e in Entry, where: e.work == ^number or e.home == ^number or e.mobile == ^number
    end

    # Total before pagination
    total = Repo.one(from e in query, select: count(e.id))

    # Paginated entries
    offset = String.to_integer(offset) - 1
    query = from e in query, limit: ^limit, offset: ^offset
    entries = Repo.all(query)

    render conn, entries: entries, total: total, offset: offset
  end

All feedback is welcome! I realise some of this belongs in the model probably.

sashaafm

sashaafm

I don’t think there’s any problem in using pattern matching in controller methods. I’ve done this in one of my projects myself and it works great:

  def insert_attachment(conn, %{"ticket_message" => ticket_message,
                                "ticket_id"      => ticket_id}) do

    ticket = Repo.get(Ticket, ticket_id)
    upload = Map.get(ticket_message, "file")
    TicketAttachmentController.insert(conn, ticket, upload)
  end

  def insert_attachment(conn, %{"ticket_id"      => ticket_id}) do

    conn
    |> put_flash(:error, "No file was selected.")
    |> redirect(to: ticket_path(conn, :show, ticket_id))
  end
NobbZ

NobbZ

Your match does only “fire” when you have all the parameters "reqsrc", "count", and "first" available. In the requested “path” /gigaset?reqsrc=auto" there is only "reqsrc" available, so you need to add another clause after your current one, which needs to be like this:

def gigaset(conn, params = %{"reqsrc" => "auto"}), do: :stuff
— 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
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
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
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

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
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews