Nicolas Grekas

Not sure what you mean @smnandre, can you elaborate or share a test case?

I'm failing to see where the lazyness happens? Where do we generate the token now? I feel like the expectations behind the term "lazy" are undefined at the moment. Anything...

OK, so you do an AJAX request to get the token. Honestly, if you rely on JS to prevent CSRF requests, you'd better use the double submit strategy.

The `{id:document}` mapping in the last example in the blog post is not needed indeed. What matters is having explicit mapping and using `{document}` should be the way to go....

Any blocker to merge this? That's remove some failures in the CI of Symfony. :pray:

@tillkruss sorry for the noise. Predis is the last dep of Symfony that didn't fix this issue. I'd love being able to close this topic :pray:

@tillkruss is there anything we could do to help get this PR merged? :pray:

BTW, this repo is an outdated fork of https://github.com/tchwork/utf8 How did you end up spotting this patch was needed? To me I'd better archive this repo and let it as...

It would be nice to move quickly on this one so that the rest of us can enjoy a deprecation-free composer experience ASAP :pray:

What about releasing v5.3.0 with the bump to 7.1?