…lowed controllers for fragments (nicolas-grekas)This PR was merged into the 6.4 branch.Discussion----------[FrameworkBundle] Add TemplateController to the list of allowed controllers for fragments| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        |Fix#52655| License       | MITForgotten in#52471Commits-------1f560bc [FrameworkBundle] Add TemplateController to the list of allowed controllers for fragments

…r (marein)This PR was squashed before being merged into the 6.4 branch.Discussion----------[HttpKernel] Allow tagged controllers in ControllerResolver| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        |Fix#52471| License       | MITIf the request attribute `_check_controller_is_allowed` is set, only `TemplateController`, children of `AbstractController` and controllers that have the attribute `#[AsController]` are allowed by default. This change also adds controllers tagged with `controller.service_arguments` to the mix. It allows them to be used with different fragment renderers (e.g. `esi` and `ssi`) without having to add any of the above conditions.This pull request is a follow up of [this discussion](#52471 (comment)).Commits-------7d2eb5a [HttpKernel] Allow tagged controllers in ControllerResolver

…r (marein)This PR was squashed before being merged into the 6.4 branch.Discussion----------[HttpKernel] Allow tagged controllers in ControllerResolver| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        | Fix #52471| License       | MITIf the request attribute `_check_controller_is_allowed` is set, only `TemplateController`, children of `AbstractController` and controllers that have the attribute `#[AsController]` are allowed by default. This change also adds controllers tagged with `controller.service_arguments` to the mix. It allows them to be used with different fragment renderers (e.g. `esi` and `ssi`) without having to add any of the above conditions.This pull request is a follow up of [this discussion](symfony/symfony#52471 (comment)).Commits-------7d2eb5a0e8 [HttpKernel] Allow tagged controllers in ControllerResolver

…ute]` attribute (GromNaN)This PR was merged into the 7.3 branch.Discussion----------[FrameworkBundle] Enable controller service with `#[Route]` attribute| Q             | A| ------------- | ---| Branch?       | 7.3| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Issues        | -| License       | MITThe `#[AsController]` attribute has 2 purposes:- Add the tag `           controller.service_argument` that configures the service and service argument injection ([RegisterControllerArgumentLocatorsPass](https://github.com/symfony/symfony/blob/79ea49c772ce4b39f414cde5648ad347c3bbcfd7/src/Symfony/Component/HttpKernel/DependencyInjection/RegisterControllerArgumentLocatorsPass.php#L56))- Allow the class in the controller resolver ([#52471](#52471))In this PR, I propose to add the tag `argument_resolver.service` on services when the class has the `#[Route]` attribute. Removing the need for `#[AsController]` on classes that use the `#[Route]` attribute.I assume that if there is a route, it is a controller.Diff (from the [docs](https://symfony.com/doc/7.2/controller/service.html)):```diff  namespace App\Controller;  use Symfony\Component\HttpFoundation\Response;- use Symfony\Component\HttpKernel\Attribute\AsController;  use Symfony\Component\Routing\Attribute\Route;- #[AsController]  class HelloController  {      #[Route('/hello', name: 'hello', methods: ['GET'])]      public function index(): Response      {          // ...      }  }```Commits-------2e59467 Enable controller service with #[Route] attribute instead of #[AsController]

…ute]` attribute (GromNaN)This PR was merged into the 7.3 branch.Discussion----------[FrameworkBundle] Enable controller service with `#[Route]` attribute| Q             | A| ------------- | ---| Branch?       | 7.3| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Issues        | -| License       | MITThe `#[AsController]` attribute has 2 purposes:- Add the tag `           controller.service_argument` that configures the service and service argument injection ([RegisterControllerArgumentLocatorsPass](https://github.com/symfony/symfony/blob/79ea49c772ce4b39f414cde5648ad347c3bbcfd7/src/Symfony/Component/HttpKernel/DependencyInjection/RegisterControllerArgumentLocatorsPass.php#L56))- Allow the class in the controller resolver ([#52471](symfony/symfony#52471))In this PR, I propose to add the tag `argument_resolver.service` on services when the class has the `#[Route]` attribute. Removing the need for `#[AsController]` on classes that use the `#[Route]` attribute.I assume that if there is a route, it is a controller.Diff (from the [docs](https://symfony.com/doc/7.2/controller/service.html)):```diff  namespace App\Controller;  use Symfony\Component\HttpFoundation\Response;- use Symfony\Component\HttpKernel\Attribute\AsController;  use Symfony\Component\Routing\Attribute\Route;- #[AsController]  class HelloController  {      #[Route('/hello', name: 'hello', methods: ['GET'])]      public function index(): Response      {          // ...      }  }```Commits-------2e594672f64 Enable controller service with #[Route] attribute instead of #[AsController]