Matthias Kurz

I think a better place to ask this question is in the repo of the Gradle Play Plugin: https://github.com/gradle/playframework/

One more thing: Even though I use a Scala `ListMap` I think it's totally ok to use it from Java as well: ```java req.attrs().getOptional(Router.Attrs.ROUTE_PARAMS) .ifPresent(pp -> System.out.println(pp.get("id").map(id -> (UUID)id).map(id ->...

@joshlemer thanks! I will change that when I continue working on this pr.

Actually this is not just about path parameters, but also about query parametes, which can also explicitly defined to get passed to an action method... Guess the naming should reflect...

@Captain1653 If we are lucky we might be able to include this into Play 2.8.8... I will have a close look asap (hopefully til monday). Meanwhile what you can do...

Alright, this is ready to review and a candidate for Play 2.8.8. The request attribute is named `ROUTE_PARAMS` (Java API) and `RouteParams` (Scala API) now. PathParams was misleading, because the...

@mergifyio backport 2.8.x

This didn't make it into 2.8.8 - however I started to work on another approach: Instead of putting the param in a classic map, we can just use the already...

@Captain1653 Thanks for bringing this up. The new approach is not generic... I will keep this in mind when I continue working on this feature. Thanks!

Reminder to not forget to unpin dependencies [marked as incompatible with Java 8 in `.scala-steward.conf`](https://github.com/playframework/playframework/blob/ce33e56107f69aaeab5a1e289712162071b4865c/.scala-steward.conf#L30). (Also check the `updates.ignore` section as well)