core VS Symfony

For instance, there are cache problems on Api Platform v3.0, so you should consider upgrading directly to the latest minor version available.

For a great setup to use as an example, see https://github.com/api-platform/core. The Behat library config is in behat.yml.dist, the feature files (process descriptions) are in the ./features directory, and the context files (Feature file Steps resolved to Context functions) can be found in ./tests/Behat.

/api/same-route is a unique identifier. Calling addPath with an existing identifier just overwrites your previous call, see https://github.com/api-platform/core/blob/main/src/OpenApi/Model/Paths.php You should call addPath once, and the instance of PathItem class should contain all HTTP methods, see constructor arguments.

We started in 2.5 and I believe I upgraded us to 2.6 just before leaving. What was with completely changing how OpenAPI generation worked in a minor release? That took a massive refactor for some of the special things were doing to hook in: https://github.com/api-platform/core/pull/3407 definitely a lot nicer to work with, but was painful for going up a minor version given our workload at the time.

Nope, not yep : https://github.com/api-platform/core/pull/1645

Let's have a look at the class EventSourceHttpClient and try to use it in Symfony\Component\Webhook\Server\Transport. It's an entirely hypothetical example to illustrate the point.

Symfony is an open-source PHP framework developed by SensioLabs which has a thriving community of over 300,000 developers with 29k stars and 9.4k forks on GitHub. It provides a set of reusable PHP components and a development methodology for building complex and scalable web applications. It is recommended due to its advanced features and user-friendly environment. The user can also develop microservices.

Symfony 7

Would be great to see for https://github.com/symfony/symfony, thanks! As that's a monorepo it may provide a challenge to the tool.

As Shopware is mostly based on the Symfony framework, which is in turn based on the PHP language, we should also consider learning about the basics, which will also be useful for other frameworks apart from Shopware, like Symfonycasts, symfony.com, php.net.

Use PHP frameworks such as Symfony. It cares about all the stuff.

Symfony is a PHP framework. https://symfony.com/

It caused much of the internal of Drupal to be re-written. This included how it was extended. With previous major versions you learned about new features and APIs. They followed mostly existing design patterns so it was easy to learn and updates your extensions for. With Symfony you had to learn whole new systems and ways of doing things. It was like learning something entirely new. And, porting extensions to it was far more work and time.

Also, the updates made Drupal slower while consuming far more system resources for the same thing. This increased costs to operate.

Internally, the kernel executes a controller, that is a callable, passing it an array of arguments. For each of these arguments, Symfony calculates its value using services that implement the ValueResolverInterface1.

Drupal is one of the content management systems aka CMS. It has long history and good stability, which is based on PHP and Symfony.