Asimov

Asimov

Hi all,

I am following along the excellent Phoenix in Action book from @geo. In page 59, while he takes us through the life cycle of a request through Phoenix, he says:

from our list of routes, /posts/:id is the path that gets you to this function. The “:id” portion of that route specifies that whatever you put into that position will be passed as the id in the params map.

But when I look at scopes in the router.ex (or the endpoint.ex file before that), I do not see the :id portion anywhere.

defmodule BlogWeb.Router do
  # ...
  scope "/", BlogWeb do
    pipe_through :browser

    get "/", PageController, :index
    resources "/posts", PostController do
      resources "/comments", CommentController, only: [:create]
    end
  end

  scope "/api", BlogWeb.API do
    pipe_through :api

    resources "/posts", PostController, only: [:index, :show]
  end
end

Is it supposed to be implied anywhere? How about if I do not what the id but another parameter. Or am I not understanding the philosophy of it?

Thanks very much!

Showing Posts 1 to 6

wolfiton

wolfiton

Your id will come from the database using a function like this in a context

ex:

def get_customer(id) do
   Customer
   |> Repo.get(id)
end

Then this function will be called in a controller.

To u8nderstand this better follow the phoenix guide here Overview — Phoenix v1.8.8

Asimov

Asimov OP

ohhh… right, reading the documentation helps. Sorry about that. So, for what I understand if I want to use another parameter what I need is to define a helper. Let’s say I have a table like this:

id      product_code
1      1001
2      1002
3      4569

and I want to be able to filter by product_code, then I would need something like this?

get "/api/:product_code", ApiController, :show

I understand it wil automatically generate this:

MyAppWeb.Router.Helpers.api_path(conn_or_endpoint, :show, "hello", some: "query")
"/api/hello?some=query"

Am I correct?

Thanks!

Asimov

Asimov OP

OK, that helps. Thank you! I do not see any of that in the provided code but as @LostKobrakai points out, it seems to be implicit. I will read the whole thing carefully to better understand the concept. Thanks again for replying.

wolfiton

wolfiton

To be able to access the resources route you need to have:

  • a migration
  • a schema
  • a controller
  • a view
  • a template.

So you use a mix generator to do that for you but those things need to exist to be able to use the resource route.

kokolegorille

kokolegorille

The following command might be useful if You want to inspect your routes.

$ mix phx.routes
— 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
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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 & 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
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews