Comparing changes

… (weaverryan) This PR was squashed before being merged into the 2.x branch. Discussion ---------- More precisely initializing services/config for asset mapper | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | Tickets | Fix #907 | License | MIT Hi! A few fixes for the new 2.9 version, which included a lot of under-the-hood changes to support asset mapper. These shouldn't be noticed by users and hopefully this will smooth out the final bumps: A) Avoid prepending the `asset_mapper` config unless FWBundle 6.3 is present. I don't love the solution - but it should work well enough, especially as this applies to asset mapper users and that is still experimental. B) Avoid registering a few asset mapper services that, on older versions of PHP/Symfony, may cause a container explosion due to a trait that won't be present. C) Plug some holes in the CI to test lower deps. The CI really needs to become much more dynamic than it is now, but this makes sure that all packages are tested for highest/lowest deps. Cheers! Commits ------- 34e7ec1 More precisely initializing services/config for asset mapper

…dling (welcoMattic) This PR was squashed before being merged into the 2.x branch. Discussion ---------- [LiveComponent] Fix array valued checkboxes change event handling | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes  | Tickets | Fix #906 | License | MIT As described in the linked issue, the event `change` of checkboxes weren't fully triggered (it didn't trigger AJAX request). It was because of the always-equals values of the pre-checked value attribute of the element and the after-change-event value of the element. Thanks `@Jim56450` for the help! Commits ------- 0e94fec [LiveComponent] Fix array valued checkboxes change event handling

…ryan) This PR was merged into the 2.x branch. Discussion ---------- Skip test if FWBundle 6.3 or higher is NOT available | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | Tickets | None | License | MIT If FWBundle 6.2 or lower is installed, then there is no AssetMapper support, so skip the test. Cheers! Commits ------- 5144b71 Skip test if FWBundle 6.3 or higher is NOT available

…ntal

…as experimental (weaverryan) This PR was squashed before being merged into the 2.x branch. Discussion ---------- [StimulusBundle] Marking only the AssetMapper integration as experimental | Q | A | ------------- | --- | Bug fix? | yesish | New feature? | no | Tickets | Addresses #907 (comment) | License | MIT StimulusBundle should not really be experimental. The `stimulus_*` Twig functions were ported from WebpackEncoreBundle and should work the same (if they don't, that would be a bug). The only part that should be experimental is the AssetMapper integration. Cheers! Commits ------- 71abb6f [StimulusBundle] Marking only the AssetMapper integration as experimental

…+ StimulusBundle

…g .add() + StimulusBundle (weaverryan) This PR was squashed before being merged into the 2.x branch. Discussion ---------- [TwigComponent] Fix breaking (deprecation instead) when using .add() + StimulusBundle | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | Tickets | None - reported on Slack. | License | MIT Accidental break if upgrading to use new StimulusBundle, but still using `attributes.add(stimulus_controller())`. Cheers! Commits ------- 88f1f05 [TwigComponent] Fix breaking (deprecation instead) when using .add() + StimulusBundle

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Comparing changes

Open a pull request

Commits on May 26, 2023

Commits on May 30, 2023

This comparison is taking too long to generate.

Uh oh!