Matthias Kurz
Matthias Kurz
I again tried to reproduce the problem, this time also with Play 3.0.2 but everything worked as expected. Tried my reproducer project which is 1:1 what you described and also...
I was looking into the PR #11244 which was supposed to fix that: However, just renaming the methods will not bind the path and the query string at the same...
@PierreAdam What was the real world use case that motivated you do open this issue? Do you want to be able to also have access to the query string params...
@amvanbaren Sure, please go for it.
@cunhazera I am closing this issue because you did not provide more information. If you do have more details to share please comment below and we may re-open the issue...
It seems quite some people watch this tracking issue, so I want to give a quick update regarding Scala 3: There are two pull requests * #11550 * #11551 (based...
So... yesterday I tagged Play 2.9.0-M3 which now publishes Scala 3 artifacts :confetti_ball: [All pull requests necessary](https://github.com/playframework/playframework/issues?q=label%3Ascala3+is%3Aclosed) were labeled with https://github.com/playframework/playframework/labels/scala3 Everyone is welcome to try it and give feedback....
Fixed already, also Play 2.7 is eol.
Fixed in the 2.9.x branch
I like the idea of running scalafmt / javafmt for all examples. We currently have that commented out: https://github.com/playframework/play-samples/blob/f2a88965af5a574edff65dc15b33b3fd954cd6f5/.github/workflows/build-test.yml#L15-L25 We could place a global scalafmt config in the root folder...