acrolink
I have already created some models and controllers using mix phx.gen.html. I need to serve context as json. My question, should I create new controllers to serve json or is it better to modify current controllers to serve html/json depending on request type?
How to create new json controllers for existing models, what is the Pheonix / Mix way to do it?
And, inside say an index method, how to check request type and serve html/json accordingly? Thanks.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
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!
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hubertlepicki
It’s one of these things that are nice in theory, but rarely work well in practice.
I would highly recommend separating your HTML-rendering controllers from API serving JSON. In my experience it usually becomes tiresome to maintain those two versions, as the HTML version will more than likely pull in more/different data than JSON version as time passes.
acrolink
mix phx.gen.jsonwith--weboption.jozzhart
mix phx.gen.html Accounts User users name:string
mix phx.gen.json Accounts User users name:string --web api --no-schema --no-context
vanceism7
The problem with
--no-schemais that (atleast as far as I’ve seen) the generated view files are empty (i.e: I have to go into the heex templates and manually add in the fields).There doesn’t happen to be some kind of
--no-migrationoption, is there? When the generator creates migration files, the migration files are somehow cached in ecto which requires cleaning the build to get things working again.Update:
Ah, I see that the migration file is also copied to
_build/your_app/priv/repo/migrations- so you have to delete the migration both from_buildandproject-root/privin order for ecto to stop trying to run it.It’d be nice if there was an option to turn off the migration file generation though. It exists on
phx.gen.schema, but not on html or json