Name already in use

* 6.1:
  chore: Add missing semicolon

* 6.0:
  chore: Add missing semicolon

* 5.4:
  chore: Add missing semicolon

This PR was submitted for the 6.2 branch but it was merged into the 5.4 branch instead.

Discussion
----------

chore: Add missing semicolon

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Commits
-------

836a973 chore: Add missing semicolon

* 6.1:
  Use SoapServer headers

This PR was merged into the 6.1 branch.

Discussion
----------

Use SoapServer headers

While debugging the istio error `Error dispatching received data: http/1.1 protocol error: HPE_UNEXPECTED_CONTENT_LENGTH` we noticed that the error was [triggered](https://github.com/nodejs/http-parser/blob/e13b274/http_parser.c#L1442) because of a duplicated Content-Length headers being send by the PHP application.
After review we noticed that the header was send by both the SoapServer and the Symfony Response for this reason I decided to open this PR.

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Commits
-------

4717f04 Use SoapServer headers

While debugging the istio error `Error dispatching received data: http/1.1 protocol error: HPE_UNEXPECTED_CONTENT_LENGTH` we noticed that the error was [triggered](https://github.com/nodejs/http-parser/blob/e13b274/http_parser.c#L1442) because of a duplicated Content-Length headers being send by the PHP application.
After review we noticed that the header was send by both the SoapServer and the Symfony Response for this reason I decided to open this PR.

…lver (ytilotti)

This PR was merged into the 6.2 branch.

Discussion
----------

[HttpKernel] [Controller] Errors on namespace value_resolver

Fix namespace on [Adding a Custom Value Resolver](https://symfony.com/doc/current/controller/value_resolver.html#adding-a-custom-value-resolver).

Commits
-------

15537d4 [Controller] Errors on namespace value_resolver

* 6.1:
  Update routing.rst

* 6.0:
  Update routing.rst

* 5.4:
  Update routing.rst

This PR was squashed before being merged into the 5.4 branch.

Discussion
----------

Update routing.rst

Add a note about allowing the http_method_override in the framework.yml file
symfony/symfony#48658

Commits
-------

576df85 Update routing.rst

This PR was squashed before being merged into the 6.2 branch.

Discussion
----------

[Doctrine] Errors on EntityValueResolver exemple

Fix exemples on [Automatically Fetching Objects (EntityValueResolver)](https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver).

Commits
-------

c7ef41e [Doctrine] Errors on EntityValueResolver exemple

* 6.1:
  Fix/bootstrap turbo docs
  Symfony CLI: add wildcard local domain information
  Symfony CLI: fix config directory path

* 6.0:
  Fix/bootstrap turbo docs
  Symfony CLI: add wildcard local domain information
  Symfony CLI: fix config directory path

* 5.4:
  Fix/bootstrap turbo docs
  Symfony CLI: add wildcard local domain information
  Symfony CLI: fix config directory path

This PR was submitted for the 6.2 branch but it was squashed and merged into the 5.4 branch instead.

Discussion
----------

Fix/bootstrap turbo docs

Add a note and code example in the "Using Bootstrap CSS & JS" docs.
If a user is using Turbo Drive with bootstrap to wrap their javascript in a `turbo:load` event listener.

Commits
-------

771dac3 Fix/bootstrap turbo docs

This PR was merged into the 5.4 branch.

Discussion
----------

Symfony CLI: fix config directory path

Symfony CLI config directory changed when Symfony CLI 5 was released, hence this change.

Commits
-------

02fc6fd Symfony CLI: fix config directory path

This PR was squashed before being merged into the 5.4 branch.

Discussion
----------

Symfony CLI: add wildcard local domain information

Commits
-------

2c49be3 Symfony CLI: add wildcard local domain information

* 6.1:
  [Form] Example of customizing EnumType labels
  Add the examples for XML and PHP config
  Update database.rst
  validator - replace expressionLanguageSyntax with new expressionSyntax

* 6.0:
  [Form] Example of customizing EnumType labels
  Add the examples for XML and PHP config
  Update database.rst

* 5.4:
  [Form] Example of customizing EnumType labels
  Add the examples for XML and PHP config
  Update database.rst

…pressionSyntax (MrYamous)

This PR was merged into the 6.1 branch.

Discussion
----------

[Validator] replace expressionLanguageSyntax with new expressionSyntax

As expressionSyntax deprecates expressionLanguageSyntax, replace it from constraint's list

[Related code PR](symfony/symfony#45623)

Commits
-------

3a35ff2 validator - replace expressionLanguageSyntax with new expressionSyntax

…isa)

This PR was submitted for the 6.1 branch but it was merged into the 5.4 branch instead.

Discussion
----------

[Form] Example of customizing `EnumType` labels

Default behavior when creating a EnumType form element is that the choice labels displayed to the user are the enum names.

This PR adds an example of how to use a function inside an enum to return labels and how to bind this function to the form element.

Commits
-------

65ece3e [Form] Example of customizing EnumType labels

Default behavior when creating a EnumType form element is that the choice labels displayed to the user are the enum names. 

This PR adds an example of how to use a function inside an enum to return labels and how to bind this function to the form element.