I'm not sure if it's exactly what you're looking for, but there was a
discussion about flexible content negotiation in this issue:
https://github.com/phoenixframework/phoenix/issues/1054
By adding a route and inspecting `conn` in the controller (just
playing with the generated Phoenix app) I can see that given a simple
GET with
`curl
http://localhost:4000/api/v1.0/resource/1.json`
there's a
`path_info: ["api", "v1.0", "resource", "1.json"]`
that you might be able to use. And then instead of the `:accepts`
plug, which seems to be working off the Accepts header, you might have
an `:extension` plug of your own that figures out what they're
requesting.
That's as far as I've gotten, and $dayjob awaits. :) Hopefully one of
the experts will chime in and help us out.
-Wendy