Nothing was named according to what it did either, I think our deploy tool was Carnival? Just codenames everywhere
Nothing was named according to what it did either, I think our deploy tool was Carnival? Just codenames everywhere
Had it with React when it moved to functional components from class components.
But I convinced myself I have to dive deep enough to understand it since a lot of people seem to like it. And now I like the Composition API more in general.
Apart from one tidbit: I constantly forget where I need to put `.value` after a variable name to extract its... value.
I have thought about how you might return normalised data to your front-end and, with support from a front-end library, rebuild the object relationships so you can access them naturally.
I looked into JSON:API and indeed there is a Laravel library for working with JSON:API https://github.com/laravel-json-api/laravel.
One place I got stuck with JSON:API is that support for updating a row and its relationships in a single API request seems to have been kicked around for a while and is unresolved: https://github.com/json-api/json-api/issues/795
There is an atomic operations extension: https://jsonapi.org/ext/atomic/
But is currently unsupported by laravel-json-api: https://github.com/laravel-json-api/laravel/issues/39
For the last year Copilot completions have been slow, unreliable and just bad, coming in at random moments, messing up syntax in dumb ways, being slow and sometimes not showing up at all. It has been painfully bad even though it used to be good. Maybe it's since they switched from Codex to the general GPTs ...