wakka_wakka
Right now I have a nested route that looks something like this:
resources "/timesheet", TimesheetController do
resources "/times", TimesController
end
And things are working as expected - if I visit
GET timesheet/${timesheet.id}/times
I get a list of all the times related to that timesheet ID. However, let’s say that I wanted to go a step further and filter it by timesheet ID and also by month. So I want the end URL to look something like this:
GET timesheet/${timesheet.id}/sept18/times
how can I nest it further? I have an assoc with times and timesheet, but what is the best approach to adding this functionality? When I tried to just add a query param, it kept throwing errors about pattern mismatch so it was pretty tough to figure out what to do next.
Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
idi527
Do you mean it threw errors for
GET timesheet/${timesheet.id}/times?date=sept18or something like that?wakka_wakka
Yeah, so basically I would want it to be sent as
GET ${timesheet.id}/${selectedMonthYr}/item, but even just doing a query parameter like you have there would be great. The error I am getting right now says that the path doesn’t exist and theres a pattern matching error, but I’m not sure how that should look.idi527
Can you post the error you get when you do
GET timesheet/${timesheet.id}/times?date=sept18or something similar? Can you also post the controller action (or just its function head) for this route?wakka_wakka
I’m at work right now so I won’t be able to post the snippets until tonight unfortunately, but I think the structure you wrote might be a little different than what I was aiming for. So how right now it goes
timesheets/:id/itemto find an item belonging to a timesheet of a certain id, I want to add one more parameter to timesheets so that it looks liketimesheets/:id/:date/itemand finds items belonging to a timesheet of a certain id, of a certain date. Does that make sense? So basically it will be a second router param to timesheet, not to itemidi527
I’m not sure if
timesheets/:id/:date/itemcan be considered “RESTful”.And
resourcesmacro exists for generating “RESTful” routes.