Maxime Steinhausser

I would love this ❤️ . Are you still working on this @CarlosGomez-dev ?

> The scroll position also jumps suddenly when used with scroll snapping. The solution for this seems to set `scroll-snap-type: none` on the panes that are not currently triggering the...

@yceruto I considered something similar in the past; I wasn't sure about reusing the same constraint but now I'd say it makes sense. And the feature would be particularly useful...

Well, no. Form transformers does allow doing such, it's true. But in their design they're expected to perform bijective transformation. Normalization is not. Events are most suitable for this. But...

> I also often have to "clean" an input (like trim or removing all spaces, including in-between) Good news are if we choose the PropertyAccessor approach, you'll indeed benefit from...

@falkenhawk : No, this PR was about allowing to provide a Serializer context per-property basis (so is about context and metadata). This issue is about a new feature that'll allow...

Regarding the issues & feature requests that echo to this one and what I encountered in my own projects, I think the use-cases are too narrowed for the PropertyAccess proposition...

Interesting ; I'm used to do the same whenever the input is not interactive (not exactly what it means, agreed) or not decorated, but I recently stumbled upon https://twitter.com/rectorphp/status/1492135257356779528?s=20&t=GZLDX4J0EwZEDnLQtlctrg. So...

Reminds me of the [`ProgressIndicator`](https://github.com/symfony/symfony/pull/12119) as well, which is yet another alternative to the `ProgressBar` in some cases, but still requires the developer to adapt the logic for CI/crons output.

Not yet. Let me add a section in https://symfony.com/doc/current/components/serializer.html in the upcoming days!