This PR was merged into the 2.x branch.

Discussion
----------

[Icons] Update composer

🤝  `@kbond`

Commits
-------

5d3bba1 [Icons] Update composer

I removed this key because it was an mistake (never used, documented, or written in recipes)

I wrongly did not consider this a BC, and it was.

So this PR re-adds the configuration key and deprecates it instead.

Should this be acceptable in a hotfix version like 2.18.1 ?

Fix #1909

…property is unitialized (smnandre)

This PR was merged into the 2.x branch.

Discussion
----------

[TwigComponent][Fix] Revert throwing exception when public property is unitialized

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| Issues        | Fix #1909
| License       | MIT

Revert #1780

If someone want to give another go at the original problem i'd appreciate.

Commits
-------

bf5959f [Fix] Revert throwing exception when public property is unitialized

This PR was merged into the 2.x branch.

Discussion
----------

[Docs][Stimulus] use camelCase for target naming

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

Hello!

I had some trouble following the doc for use `stimulus_target` and how to use them inside my stimulus controller.

As we can see [on the stimulus target doc](https://stimulus.hotwired.dev/reference/targets#naming-conventions), the value of target should be in camelCase as it's mapped in property in the controller.

IE
```
<div data-my-controller-target="myElement">
```

```
import { Controller } from "`@hotwired`/stimulus"

export default class extends Controller {
  static targets = [ "myElement"]
  // …
  foo() {
	this.myElementTarget.innerHTML = "...";
  }
}
```

So in this PR, I changed examples for `stimulus_target` usage.

Commits
-------

4867dd1 [Docs][Stimulus] use camelCase for target naming

…nandre)

This PR was merged into the 2.x branch.

Discussion
----------

[Fix] Revert removing `twig_component.controllers_json`

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| Issues        | Fix #
| License       | MIT

I [removed](https://github.com/symfony/ux/pull/1823/files) this key because it was an [mistake](0284c0a) (never used, documented, or written in recipes)

I wrongly did not consider this a BC break, and it was.

This PR re-adds the configuration key and deprecates it instead.

--

Should this be acceptable in a hotfix version like 2.18.1 ?

Commits
-------

6c397d5 [Fix] Revert removing `twig_component.controllers_json`

…(maelanleborgne)

This PR was merged into the 2.x branch.

Discussion
----------

[Translator] Fix changing dump directory using AssetMapper

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| Issues        | Fix #1642
| License       | MIT

The configuration node `ux_translator.dump_directory` wasn't correctly taken into account when using UxTranslator with AssetMapper.
This PR fixes the configuration prepend of AssetMapper to use the custom path + adds a "caution" section in the docs to remind developers to also update their `importmap.php`.

Commits
-------

a27cfc8 Fix changing dump directory using AssetMapper

…fix (WebMamba)

This PR was merged into the 2.x branch.

Discussion
----------

[LiveComponent] accept live component Content-Type with suffix

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| Issues        | Fix #1902
| License       | MIT

Commits
-------

044f338 [LiveComponent] accept live component Content-Type with suffix