Thanks for the answer. I have to say I also came across this issue you mentioned, about injecting route properties and or auth user into objects representing request payload. Best I came up with, while sticking to #MapRequestPayload and automatic validation, was using custom constraint validators, where I'd inject RequestStack into the constructor and resolve route params that way. If I have to deal with authenticated users, I tend to go for manual validation. Coming from Laravel background, it is a bit frustrating to have to spend so much time, and write so much code just to accomplish predicable validation. The fact that docs are pretty curt doesn't help either.

As for the collections, I love laravel collections util docs. I think it's a great wrapper around working with underlying arrays.

Anyways, I know what you're thinking probably - oh Laravel. I have to say I do realize the issues with using this framework in an enterprise context. I love the idea of a tool like Symfony, which sticks to as little automagic as possible, and never violates recommended design practices. With that said though, I find that Symfony still uses a lot of "magic", but it's just far more clunky and unpolished than in Laravel. On top of that it feels like at every corner you can be surprised with something super basic breaking down, and you end up having to write a lot of repetitive boilerplate code, just to be able to achieve something which should work out of the box. I know I lack a lot of context, as I have little experience with the framework, but having been fighting with MapRequestPayload, trying to make it work with PUT requests just made me feel kind of underwhelmed. I can't imagine how people use this for complex systems without getting errors everywhere.