Params in the URL and body -- how does Phoenix handle them together?

You can use body_params from conn, I think.

1. Do “params” always contain only the query string/params - from the URL?

2. Can “params” contain body params instead or in addition to Query String params?

But that’s for Plug!

Phoenix uses plug!

Try this

def my_post_handler(%Plug.Conn{body_params: body_params} = conn, _body_and_query_params) do
  # ...
end

Do “params” always contain only the query string/params - from the URL?

In phoenix controller “actions”, the second argument by default contains both body and query params.

And how can I distinguish between query and body params?

conn.body_params or conn.query_params

And how can I distinguish between query and body params?

You can’t if you use the second argument in a phoenix controller action.

For note, Phoenix is just ‘more’ on plug, it still uses the plug interfaces, plug calls, plug everything, it just adds things like a templating system and websockets an such.

As an aside, I wish Phoenix URL arguments came in the param map via atom keys, where query arguments came in via string keys…

How do you propose to implement this safely without some major macro witchcraft? Namely something lime rewriting function heads so that pattern matches with maps become pattern matches with strings or something like that?