See the list of my latest blog posts.
With Guzzle v7, its class
GuzzleHttp\Client became annotated as
@final as it will be a real
final class in Guzzle
v8. Extending Guzzle clients to enrich them with custom functionality or to pass configuration (e.g. API credentials) is
now discouraged and static code analysis tools like PHPStan may report this as an error. Depending on how
GuzzleHttp\Client is extended, migration may be cumbersome. I got your back, and I'll cover some common cases in this
As stated in the previous article, you may also use PSR-7 for AJAX requests. However, the implementation in the backend and the frontend is different. This article explains how you setup so-called "routes" for backend AJAX requests and how eIDs look like for the frontend.
Ah, you have a non-extbase extension whose content is cleanly structured into Classes, Configuration, Resources, etc. But then there are these pesky
modX/index.php files for your backend modules. That's not nice, but there is help: PSR-7. This tutorial shows how to setup your backend modules according to PSR-7.