I’ll definitely look into that, seems interesting. I have used responderbecause i found it easy to create transformers and malformate response data, but it seems like things are already integrated, including the relationship part. Also, for namings, instead of index, store, update, etc. i thought that might be more semantic way of the things that the route actually do (getUsers, createUser) since it’s more expressive. But i’ll definitely switch to the Resources if they seem better :D

Minimalist Laravel developer. Full stacking with AWS and Vue.js. Sometimes I deploy to Kubernetes. 🚢

Minimalist Laravel developer. Full stacking with AWS and Vue.js. Sometimes I deploy to Kubernetes. 🚢