gmc
I’m implementing a GET request to return a list of database records like the standard “index” method generated by phx.gen. But my method should filter the result, i.e. the client requests only a specific set of IDs. At first, I wanted to send the list of IDs in a JSON array in the request body, but I’ve seen that the specification for GET doesn’t recommend to have any body (and Phoenix does not return it by default).
So my guess is I should probably use URL query string, but I’m not sure how to format it, that my Phoenix controller can easily extract it as an array.
Example: Let’s say I want to request the list for IDs “12bb23d2-81fe-445b-bf5e-2716f582fbb0” and “654802aa-4515-4b52-b9a1-d74bf43f074b”.
Would the URL be something like
a) /api/sync/?ids=“12bb23d2…”,“654802aa…”
b) /api/sync/?ids=“12bb23d2…”&ids=“654802aa…”
c) /api/sync/?ids=“12bb23d2…”&ids=“654802aa…”
d) …
And how would you read that in the controller?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Develop your skills with books, videos, and courses.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 2 of 2 Posts
Nicd
Try option c, it should be supported by default in Phoenix IIRC. You should be able to find the array in the request params like
%{"ids" => ["12bb23d2...", "654802aa..."]}.gmc
Brilliant, works as expected without any special parsing. Thanks!