…icolas-grekas)This PR was merged into the 3.4 branch.Discussion----------[Routing] Add PHP fluent DSL for configuring routes| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -If we add a PHP DSL for DI config (#23834), we must have a similar one for routing. Here it is. See fixtures.So, you always start with a `RoutingConfigurator $routes`, which allows you to:```php$routes->add($name, $path); // adds a route$routes->import($resource, $type = null, $ignoreErrors = false); // imports routes$routes->collection($name = ''); // starts a collection, all *names* might be prefixed```then- for "import" and "collection", you can `->prefix($path)`;- for "add" and "collection", you can fluently "add" several times;- for "collection" you add sub"`->collection()`";- and on all, you can configure the route(s) with:```php->defaults(array $defaults)->requirements(array $requirements)->options(array $options)->condition($condition)->host($pattern)->schemes(array $schemes)->methods(array $methods)->controller($controller)```Commits-------f433c9a [Routing] Add PHP fluent DSL for configuring routes

…iner (nicolas-grekas)This PR was merged into the 3.4 branch.Discussion----------[DI] Add "PHP fluent format" for configuring the container| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#22407| License       | MIT| Doc PR        | -This PR allows one to write DI configuration using just PHP, with full IDE auto-completion.Example:```phpnamespace Symfony\Component\DependencyInjection\Loader\Configurator;use Symfony\Component\DependencyInjection\Tests\Fixtures\Prototype\Foo;return function (ContainerConfigurator $c) {    $c->import('basic.php');    $s = $c->services()->defaults()        ->public()        ->private()        ->autoconfigure()        ->autowire()        ->tag('t', array('a' => 'b'))        ->bind(Foo::class, ref('bar'))        ->private();    $s->set(Foo::class)->args([ref('bar')])->public();    $s->set('bar', Foo::class)->call('setFoo')->autoconfigure(false);};```Commits-------814cc31 [DI] Add "PHP fluent format" for configuring the container

…es_{env} with php extension (helyakin)This PR was merged into the 6.4 branch.Discussion----------[HttpKernel] when configuring the container add services_{env} with php extension| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | none| License       | MITHello the communityThis is my first PR attempt.So after reading this [documentation](https://symfony.com/doc/current/service_container.html#remove-services) and unsuccessfully trying to load my `service_test.php`, I've noticed that the `configureContainer(..)` function in the `MicroKernelTrait` file was not configured to automatically load this file.So either we should fix the documentation, either we should fix the configuration.Since this the [framework-bundle](https://github.com/symfony/framework-bundle) is backed by [Alximy](https://alximy.io) I figured it would be cool 😎 to try and fix 🐛 the configuration.Anyway share me your thoughts about what should be done !And I wanted to say that php service configuration is 🔥 so shoutout to the one who did this (I think it's you `@nicolas`-grekas with this [PR](#23834) right ? 💪🏻)Also big thanks to `@jeremyFreeAgent` for debugging this with me and `@HeahDude` for showing me the php service configuration PR.Commits-------4aac1d9 🐛 (kernel) when configuring the container add services with php ext

…es_{env} with php extension (helyakin)This PR was merged into the 6.4 branch.Discussion----------[HttpKernel] when configuring the container add services_{env} with php extension| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | none| License       | MITHello the communityThis is my first PR attempt.So after reading this [documentation](https://symfony.com/doc/current/service_container.html#remove-services) and unsuccessfully trying to load my `service_test.php`, I've noticed that the `configureContainer(..)` function in the `MicroKernelTrait` file was not configured to automatically load this file.So either we should fix the documentation, either we should fix the configuration.Since this the [framework-bundle](https://github.com/symfony/framework-bundle) is backed by [Alximy](https://alximy.io) I figured it would be cool 😎 to try and fix 🐛 the configuration.Anyway share me your thoughts about what should be done !And I wanted to say that php service configuration is 🔥 so shoutout to the one who did this (I think it's you `@nicolas`-grekas with this [PR](symfony/symfony#23834) right ? 💪🏻)Also big thanks to `@jeremyFreeAgent` for debugging this with me and `@HeahDude` for showing me the php service configuration PR.Commits-------4aac1d9fee 🐛 (kernel) when configuring the container add services with php ext

…es_{env} with php extension (helyakin)This PR was merged into the 6.4 branch.Discussion----------[HttpKernel] when configuring the container add services_{env} with php extension| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | none| License       | MITHello the communityThis is my first PR attempt.So after reading this [documentation](https://symfony.com/doc/current/service_container.html#remove-services) and unsuccessfully trying to load my `service_test.php`, I've noticed that the `configureContainer(..)` function in the `MicroKernelTrait` file was not configured to automatically load this file.So either we should fix the documentation, either we should fix the configuration.Since this the [framework-bundle](https://github.com/symfony/framework-bundle) is backed by [Alximy](https://alximy.io) I figured it would be cool 😎 to try and fix 🐛 the configuration.Anyway share me your thoughts about what should be done !And I wanted to say that php service configuration is 🔥 so shoutout to the one who did this (I think it's you `@nicolas`-grekas with this [PR](symfony/symfony#23834) right ? 💪🏻)Also big thanks to `@jeremyFreeAgent` for debugging this with me and `@HeahDude` for showing me the php service configuration PR.Commits-------4aac1d9fee 🐛 (kernel) when configuring the container add services with php ext

… format for semantic configuration (nicolas-grekas)This PR was merged into the 7.4 branch.Discussion----------[Config][DependencyInjection] Deprecate the fluent PHP format for semantic configuration| Q             | A| ------------- | ---| Branch?       | 7.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Issues        | -| License       | MITThis PR deprecates the fluent PHP format for semantic configuration introduced in Symfony 5.4 by `@Nyholm` (see#40600).It aims to replace it with the new array-based PHP config format (see#61490).The fluent PHP config format was a great experiment:- It helped us improve the Config component and the code generation of fluent config builders.- It confirmed the community’s interest in PHP-based configuration.- And it showed us its limits.Those limits are structural. Writing fluent config is difficult and full of edge cases. Its rigidity comes from having to match one canonical interpretation of the semantic config tree. Automatic code generation can’t capture the custom logic that before-normalizers introduce, yet those normalizers are essential for flexibility and backward compatibility. This rigidity makes fluent config fragile. How do we deal with this fragility as config tree authors? At the moment, we don't care. Maybe this format is too niche for you to have experienced this issue, but we cannot guarantee that simple upgrades won't break your fluent PHP config.The new array-based PHP format builds directly on the same code used for loading YAML configs.That means:- trivial conversion between YAML and PHP arrays,- identical flexibility and behavior,- and support for auto-completion and static analysis through generated array shapes.The generated array shapes are rigid too, but that rigidity is non-breaking: even if your config no longer matches the canonical shape, your app keeps working. Static analyzers might warn you: that’s an invitation to update, not a failure.I'm submitting this PR a bit l late for 7.4 but I think it's important to merge now. Deprecating the fluent PHP config format will:- prevent new code from relying on a fragile approach,- make room in the documentation for the array-based format,- and consolidate Symfony’s configuration story around a robust PHP-based format.Fluent PHP for semantic config served us well but it's time to retire it.   ```diff   -return function (AcmeConfig $config) {   -    $config->color('red');   -}   +return new AcmeConfig([   +    'color' => 'red',   +]);   ```PS: there's another fluent config format for services and routes (see#23834 and#24180). This other format is handwritten. It doesn't have the issues listed above and it is *not* deprecated. It's actually the recommended way *for bundles* to declare their config (instead of XML, see#60568).Commits-------332b4ac [Config][DependencyInjection] Deprecate the fluent PHP format for semantic configuration