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 e…

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 …

[image] acrolink: How to create new json controllers for existing models, what is the Pheonix / Mix way to do it? mix phx.gen.json with --web option.

mix phx.gen.html Accounts User users name:string mix phx.gen.json Accounts User users name:string --web api --no-schema --no-context [image] Best practice for phoenix project with HTML and JSON endpoints Questions I stumbled here a little late, but you can sk…

The problem with --no-schema is 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-migration option, is there? When the generator creates migration files, the …

Should separate controllers be used to render HTML and JSON results for same entity types?

Questions & Help Questions

acrolink October 8, 2017, 9:03pm 3

mix phx.gen.json with --web option.