gitea

Commit Graph

Author	SHA1	Message	Date
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.	2 years ago
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.	2 years ago

Author

SHA1

Message

Date

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.

2 years ago

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.

2 years ago

2 Commits (45b1f4dd3ba898decbc3472b78bac081e6833cca)