mirrors/forgejo

Fork 0

mirror of https://codeberg.org/forgejo/forgejo.git synced 2025-08-24 11:13:47 +00:00

Commit graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Giteabot	2d1a7e1cd4	Introduce ctx.PathParamRaw to avoid incorrect unescaping (#26392 ) (#26405 ) Backport #26392 by @wxiaoguang Fix #26389 And complete an old TODO: `ctx.Params does un-escaping,..., which is incorrect.` Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2023-08-09 07:31:44 +00:00
silverwind	24e64fe372	Replace `interface{}` with `any` (#25686 ) (#25687 ) Same perl replacement as https://github.com/go-gitea/gitea/pull/25686 but for 1.20 to ease future backporting.	2023-07-04 23:41:32 -04:00
wxiaoguang	6b33152b7d	Decouple the different contexts from each other (#24786 ) Replace #16455 Close #21803 Mixing different Gitea contexts together causes some problems: 1. Unable to respond proper content when error occurs, eg: Web should respond HTML while API should respond JSON 2. Unclear dependency, eg: it's unclear when Context is used in APIContext, which fields should be initialized, which methods are necessary. To make things clear, this PR introduces a Base context, it only provides basic Req/Resp/Data features. This PR mainly moves code. There are still many legacy problems and TODOs in code, leave unrelated changes to future PRs.	2023-05-21 09:50:53 +08:00

Giteabot

2d1a7e1cd4

Introduce ctx.PathParamRaw to avoid incorrect unescaping (#26392 ) (#26405 )

Backport #26392 by @wxiaoguang

Fix #26389

And complete an old TODO: `ctx.Params does un-escaping,..., which is
incorrect.`

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>

2023-08-09 07:31:44 +00:00

silverwind

24e64fe372

Replace interface{} with any (#25686 ) (#25687 )

Same perl replacement as https://github.com/go-gitea/gitea/pull/25686
but for 1.20 to ease future backporting.

2023-07-04 23:41:32 -04:00

wxiaoguang

6b33152b7d

Decouple the different contexts from each other (#24786 )

Replace #16455

Close #21803

Mixing different Gitea contexts together causes some problems:

1. Unable to respond proper content when error occurs, eg: Web should
respond HTML while API should respond JSON
2. Unclear dependency, eg: it's unclear when Context is used in
APIContext, which fields should be initialized, which methods are
necessary.


To make things clear, this PR introduces a Base context, it only
provides basic Req/Resp/Data features.

This PR mainly moves code. There are still many legacy problems and
TODOs in code, leave unrelated changes to future PRs.

2023-05-21 09:50:53 +08:00

3 commits