… 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

… to assist in writing and discovering app's configuration (nicolas-grekas)This PR was squashed before being merged into the 7.4 branch.Discussion----------[FrameworkBundle] Auto-generate `config/reference.php` to assist in writing and discovering app's configuration| Q             | A| ------------- | ---| Branch?       | 7.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Doc PR |symfony/symfony-docs#21511| License       | MITThis PR reverts#61490 and#61885, and builds on#61894.These reverts explain a big chunk of the attached patch.This adds a compiler pass that generates a `config/reference.php` file.This file contains two classes that define array-shapes for app's and routing configuration.Part of these shapes are auto-generated from the list of bundles found in `config/bundles.php`.The `config/reference.php` file should be loaded by a new line in the "autoload" entry of composer.json files: `"classmap": ["config/"]` - recipe update pending. This means that the file should be committed. This is on purpose: as the name suggests, this file is also a config reference for human readers. Having to commit the changes is also a nice way to convey config improvements to the community - at least for ppl that review their commits ;). It also solves a discovery problem that happens with phpstan/etc having a hard time to find the classes currently generated for config builders in the cache directory.With this PR, `config/services.php` could start as such:```php<?phpnamespace Symfony\Component\DependencyInjection\Loader\Configurator;return App::config([    'services' => [        'App\\' => [            'resource' => '../src/'        ],    ],]);```and `config/routes.php` would start as:```php<?phpnamespace Symfony\Component\Routing\Loader\Configurator;return Routes::config([    'controllers' => [        'resource' => 'attributes',        'type' => 'tagged_services',    ]]);```The generated shapes use advanced features that are not fully supported by phpstan / phpstorm. But the gap should be closed soon.PS:https://symfony.com/blog/new-in-symfony-7-4-deprecated-xml-configuration will need an update.Commits-------22349f5 [FrameworkBundle] Auto-generate `config/reference.php` to assist in writing and discovering app's configuration