router contrib #8

New Issue

tjp · 2023-01-12T16:51:50Z

tjp commented

2023-01-12 16:51:50 +00:00

IMO this is worth taking a dependency for, in order to get a good radix tree implementation (without having to write it).

There's a lot here to figure out from a requirements standpoint, but here are a few thoughts.

chi is a great example to try and follow, usability-wise
building or mounting sub-routers is a great ux - allows for composing independently-developed applications well
- application A is built with relative links between its pages, its go API exposes a Router
- application B: same thing
- server author can simply mount A's router at /a/* and B at /b/*

IMO this is worth taking a dependency for, in order to get a good radix tree implementation (without having to write it). There's a lot here to figure out from a requirements standpoint, but here are a few thoughts. * [chi](https://pkg.go.dev/github.com/go-chi/chi/v5) is a great example to try and follow, usability-wise * [building or mounting sub-routers](https://pkg.go.dev/github.com/go-chi/chi/v5#Router.Route) is a great ux - allows for composing independently-developed applications well * application A is built with relative links between its pages, its go API exposes a Router * application B: same thing * server author can simply mount A's router at `/a/*` and B at `/b/*`

tjp changed title from ~~router~~ to router contrib

2023-01-12 16:52:48 +00:00

tjp added this to the v1.0 milestone 2023-01-14 18:04:53 +00:00

tjp added the

enhancement

label 2023-01-14 18:05:30 +00:00

tjp added this to the (deleted) project 2023-01-19 20:58:36 +00:00

tjp modified the milestone from v1.0 to 1.x

2023-01-25 03:04:35 +00:00

tjp added reference router

2023-02-03 00:12:16 +00:00

tjp closed this issue