@mkurz hi! I’m interested in working on these issues and would love to help make twirl templates more scala3 friendly. If you have any guidance or suggestions on how to get started, I’d really appreciate it! 🥰

regardingthis issue, my current thinking is to somehow check whether the definition site usesimplicit/using, and then try prependingusing to whatever the last parameter() is at the call site. That said, this approach feels a bit crude/ugly, especially since the parser doesn’t currently recognizeusing. So maybe that's where I should start?

what would be the ideal way to approach this?

(LSP support for play specific files like twirl and routes are a part of my summer project so I have vested interest in making the experience better 😅)

All tests and scripted tests pass with 3.7.2-RC1