I love InertiaJS to the point where it's becoming a personality trait I tend to want to...
I love InertiaJS to the point where it's becoming a personality trait
I tend to want to use it for everything, but adding Inertia to an existing Laravel API gets awkward fast. Same thing happens in the other direction: you start with a full Inertia frontend and then realize you want to expose some of that data as a public API too.
The naive solutions are:
Sprinkle if ($request->wantsJson()) into your controllers
Maintain two separate routes that return the exact same data
Modern web development often pushes teams toward separation. A product may have a separate backend,...
The Polymorphic Spaghetti Trap When building enterprise SaaS platforms at Smart Tech Devs, you often...
If you work with APIs, JSON data is everywhere. From API responses and configuration files to test...
The Persistent Memory Trap Traditional PHP was designed to die. At Smart Tech Devs, a standard...
Mastering Laravel Performance: A Deep Dive into Eager Loading for N+1 Query Prevention ...
I got tired of pasting API responses into random formatter sites without knowing where the data goes,...
