Level 50
Jun 19, 2019
3
Level 1
API
Is there a way to avoid writing json responses in every controller as a response.
Is it possible to encapsulate all the data and functionally maybe using calls in a Middleware or something like; 'Accept': 'application/json' through headers.
Separating the view from the application is something that I would still like to do right now. If so, please provide me with a code example of how I would go about such.
Level 1
@AURAWINDSURFING - What do you mean?
Level 4
If you just return the model from your controller, it will be converted to an array, and in the case of JSON requests, come back as JSON. I guess in theory you could write a middleware that would return any requested model this way. Many of the entry level Laravel tutorials show you how to return a model directly from a route, I guess you’ve seen that. So something like that, but for all models.
I think in reality, you would want to have more control over how each model is represented as JSON. That’s where Resources are useful. See https://laravel.com/docs/5.8/eloquent-resources
Also, controllers are a good place for authorization and validation (perhaps with the help of Policies and Requests), which may vary from model to model. And if your API will not only retrieve data, but also create, update, delete, and so on, I think you would need a controller either way. And then the “retrieve” part is usually very simple compared to create or update, for instance.
2 likes
Please or to participate in this conversation.