silverdr
Looking for a way to distinguish whether e. g. document.html or document.pdf was requested and to serve appropriate content format in return. Something akin to respond_to in that other framework. I think I solved it already before but I can’t recall now. Hints/pointers appreciated.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
silverdr
Yes, I read this one but still don’t feel like this answers it, especially in the context of “viewless” Phx, which is what everybody believes to be the future, man
Also don’t recall making multiple “Views” for that purpose but if there are no other answers then maybe memory doesn’t serve
LostKobrakai
The need for multiple modules comes from the fact that function components normalized to arity-1 functions (
NameSpaceFormat.name(assigns)), which receive only assigns. There’s no additional parameter anymore, which would pass the format to the function transforming assigns to the format being rendered. Switching by format now happens on the view/layout/root layout level withput_view/put_layout/put_root_layoutand them being updated to accept keyword lists.Phoenix.Viewhadrender("name.format", assigns), which could switch on format within the same module. If you want to retain that you can keep usingPhoenix.Viewby manually depending on it.In regards to “viewless phx” I’m not sure what you’re refering to. Yes
Phoenix.Viewis no longer used, but you can and likely will have modules serving the purpose of views still. Personally I’m a fan of phoenix having changed to dumping those modules next to controllers though, as it makes that fact less discoverable. I guess the tldr there would be: On a high level nothing changed (views are still a thing), but the implementation changed.silverdr
Ah, that would explain. So this in fact changed, which might be the reason why in the recent docs I couldn’t find how I think I did it previously. TNX