Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week
Source: matthewdaly.co.uk
Don't use stdClassCategory: Laravel, PHP, api
The digital agency I work for specialises in marketing, so some of my work tends to relate to mailing lists. Now, this was an implementation detail of the Campaign Monitor PHP SDK, which is old and creaky (to say the least..).
It's trivial to define a named exception and use that to specify the type of exception, and you can then capture exceptions to handle them differently elsewhere in the application.
If an API client returns an instance of stdClass, that doesn't tell me anything about what that object is.
Hopefully, this has made it clear how compelling it is to use named classes instead of stdClass, and how much benefit you can get from not just using named classes, but creating your own base container class for them.
It's trivial to define a named exception and use that to specify the type of exception, and you can then capture exceptions to handle them differently elsewhere in the application.
If an API client returns an instance of stdClass, that doesn't tell me anything about what that object is.
Hopefully, this has made it clear how compelling it is to use named classes instead of stdClass, and how much benefit you can get from not just using named classes, but creating your own base container class for them.
Newsletter
Glimpse
Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Community Partners
Laravel/PHP Careers