5 ms·
As a Laravel user, I agree with you completely. Laravel for API, Next.js/Nuxt.js to handle the frontend. It avoids depending on Laravel-<insert-name> frontend t
by fraktl 5y ago
As a Laravel user, I agree with you completely. Laravel for API, Next.js/Nuxt.js to handle the frontend. It avoids depending on Laravel-<insert-name> frontend tool/framework/you-name-it.
- dncornholio 5y agoExactly, being able to pick your own frontend is what makes Laravel so useful to me. I hope they will give API functionality the same love and attention some day.
- mimsee 5y agoWhat type of API functionality would you like to see?
- dncornholio 5y agoSwagger integration or something similar that generates documentation and live testing based on OpenAPI. Some support for endpoint versioning. Better ways to serialize models that have properties with computed values, on a specific request. ($_appends and $_hidden properties are getting a mess in complex projects). Plus, I'm sure people can up with more things I never knew I needed!