diff options
| author | wxiaoguang <wxiaoguang@gmail.com> | 2023-07-19 02:14:47 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-18 18:14:47 +0000 |
| commit | 236c645bf16754ca9294545e71014a01a24ccfd8 (patch) | |
| tree | 4ca9d8f93aca854d841a7379955e9653a8212546 /templates | |
| parent | 265a28802a6062d86964c9bfe1959437eaf69afb (diff) | |
| download | gitea-236c645bf16754ca9294545e71014a01a24ccfd8.tar.gz gitea-236c645bf16754ca9294545e71014a01a24ccfd8.zip | |
Refactor "Content" for file uploading (#25851)
Before: the concept "Content string" is used everywhere. It has some
problems:
1. Sometimes it means "base64 encoded content", sometimes it means "raw
binary content"
2. It doesn't work with large files, eg: uploading a 1G LFS file would
make Gitea process OOM
This PR does the refactoring: use "ContentReader" / "ContentBase64"
instead of "Content"
This PR is not breaking because the key in API JSON is still "content":
`` ContentBase64 string `json:"content"` ``
Diffstat (limited to 'templates')
| -rw-r--r-- | templates/swagger/v1_json.tmpl | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/templates/swagger/v1_json.tmpl b/templates/swagger/v1_json.tmpl index 4c6ee55f84..b7620b9e76 100644 --- a/templates/swagger/v1_json.tmpl +++ b/templates/swagger/v1_json.tmpl @@ -16125,7 +16125,7 @@ "content": { "description": "new or updated file content, must be base64 encoded", "type": "string", - "x-go-name": "Content" + "x-go-name": "ContentBase64" }, "from_path": { "description": "old path of the file to move", @@ -16810,7 +16810,7 @@ "content": { "description": "content must be base64 encoded", "type": "string", - "x-go-name": "Content" + "x-go-name": "ContentBase64" }, "dates": { "$ref": "#/definitions/CommitDateOptions" @@ -21687,7 +21687,7 @@ "content": { "description": "content must be base64 encoded", "type": "string", - "x-go-name": "Content" + "x-go-name": "ContentBase64" }, "dates": { "$ref": "#/definitions/CommitDateOptions" |