wxiaoguang b9a97ccd0e Refactor web route (#24080) ... The old code is unnecessarily complex, and has many misuses. Old code "wraps" a lot, wrap wrap wrap, it's difficult to understand which kind of handler is used. The new code uses a general approach, we do not need to write all kinds of handlers into the "wrapper", do not need to wrap them again and again. New code, there are only 2 concepts: 1. HandlerProvider: `func (h any) (handlerProvider func (next) http.Handler)`, it can be used as middleware 2. Use HandlerProvider to get the final HandlerFunc, and use it for `r.Get()` And we can decouple the route package from context package (see the TODO). # FAQ ## Is `reflect` safe? Yes, all handlers are checked during startup, see the `preCheckHandler` comment. If any handler is wrong, developers could know it in the first time. ## Does `reflect` affect performance? No. https://github.com/go-gitea/gitea/pull/24080#discussion_r1164825901 1. This reflect code only runs for each web handler call, handler is far more slower: 10ms-50ms 2. The reflect is pretty fast (comparing to other code): 0.000265ms 3. XORM has more reflect operations already		2023-04-20 14:49:06 -04:00
..
install.go	Refactor cookie (#24107)	2023-04-13 15:45:33 -04:00
routes.go	Refactor web route (#24080)	2023-04-20 14:49:06 -04:00
routes_test.go	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
setting.go	Use a general approach to access custom/static/builtin assets (#24022)	2023-04-12 18:16:45 +08:00