We've released version 4.0.0 of the PHP SDK for accessing our geocoding API

Some major improvements/changes, please see the details on the blog:
https://blog.opencagedata.com/post/new-release-our-php-geocoding-sdk

#php #geocoding

As always, if PHP is not your cup of tea 🫖, don't worry, we also have SDKs for over 40 other languages and frameworks:

https://opencagedata.com/sdks

@opencage interesting! Why have you decided to use Guzzle instead of the abstract/independent `php-http/discovery`?
@tobiaskoengeter @opencage The async feature mostly, the code modernization kept growing and growing and at some point I had to stop myself and create a release before users get overwhelmed. Main goal was getting rid of the old curl methods, then adding async. Version 5 will likely support PSR 7 and 18 which I think is the abstract php-http. (OpenCage API is written in Perl, we don't use PHP ourselves much though I did develop in it professional a couple of years, around Laravel 4/5).
@mtmail @tobiaskoengeter @opencage as co-author of psr-18: i would have loved to provide async support, the problem is we lack a psr for promises, which are the foundation for async, and a async psr really should not include promises as an add-on.
@dbu @mtmail @opencage Yes, you're right. But PSR-18 is bound to be updated one day, or there'll be a new one!
@tobiaskoengeter @mtmail @opencage i do hope so, and if a promise psr ever happens, i'd be happy to contribute to a async http psr
@mtmail @opencage I understand that – you have to start somewhere and get results. Thanks to semantic versioning, changes can be introduced without any problems. And there’s always room for improvement. 😊