Provide shortcut methods for routing [SPR-14953]

[spring-projects-issues]

Sébastien Deleuze opened SPR-14953 and commented

Currently, we declare routes like that:

route(GET("/foo/**"), r -> ok().body(fromObject("foo")))
		.andRoute(GET("/bar/**"), r -> ok().body(fromObject("bar")))
		.andRoute(POST("/baz/**"), r -> ok().body(fromObject("baz")))

This is a very common use case that deserves IMO syntactic sugar to make routes more readable and maintainable. Something like:

routeGet("/foo/**", r -> ok().body(fromObject("foo"))
		.andRouteGet("/bar/**", r -> ok().body(fromObject("bar"))
		.andRoutePost("/baz/**", r -> ok().body(fromObject("baz"))

That will still allow to use the current more powerful/evolutive API while providing some nice shortcuts for this kind of code that application developers will have to write so many times.

---

Issue Links:

• Improve nested routes API [SPR-14954] #19521 Improve nested routes API

1 votes, 3 watchers

[spring-projects-issues]

Sébastien Deleuze commented

PR created with code samples.

[spring-projects-issues]

Sébastien Deleuze commented

Postponed to RC1 in order to wait user feedbacks.

[spring-projects-issues]

Sébastien Deleuze commented

After more thoughts, given the small improvement my proposal allow while being less flexible (can't specify media type, etc.), I prefer to postpone this question to 5.1 and provide a real Kotlin routing DSL as part of #19631 for 5.0.

[spring-projects-issues]

Arjen Poutsma commented

I don't think that this is the right way for the API to evolve. It would add 7 new default methods to RouterFunction, which would actually make the other methods less visible. And it also hides the RequestPredicate type, which I think is rather important to know about.