gitea

Commit Graph

Author	SHA1	Message	Date
6543	8995046110	Less naked returns (#25713 ) just a step towards #25655 and some related refactoring	1 year 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
wxiaoguang	023a048f52	Make repository response support HTTP range request (#24592 ) Replace #20480 Replace #18448 Close #16414	2 years ago

Author

SHA1

Message

Date

6543

8995046110

Less naked returns (#25713 )

just a step towards  #25655

and some related refactoring

1 year 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

wxiaoguang

023a048f52

Make repository response support HTTP range request (#24592 )

Replace #20480
Replace #18448

Close #16414

2 years ago

3 Commits (f77b4cb4a2bbaeda4035903c73675b3d9aaab3b2)