[PR #23] [MERGED] Using lowercase keys in bucketResponse struct json #275

New issue

Closed

opened 2026-03-03 12:10:01 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 12:10:01 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fsouza/fake-gcs-server/pull/23
Author: @teone
Created: 3/27/2019
Status: ✅ Merged
Merged: 3/28/2019
Merged by: @fsouza

Base: master ← Head: master

📝 Commits (1)

f5c4d3c Using lowercase keys in bucketResponse struct json

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 fakestorage/response.go (+2 -2)

📄 Description

Google Cloud Storage REST APIs use lowercase keys in json bucket response.
This will get the fake server to work with the GCS library.
Without this client.list_buckets() is returning:

[<Bucket: None>, <Bucket: None>]

with this patch:

[<Bucket: another-bucket>, <Bucket: bucket>]

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fsouza/fake-gcs-server/pull/23 **Author:** [@teone](https://github.com/teone) **Created:** 3/27/2019 **Status:** ✅ Merged **Merged:** 3/28/2019 **Merged by:** [@fsouza](https://github.com/fsouza) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`f5c4d3c`](https://github.com/fsouza/fake-gcs-server/commit/f5c4d3cb21f2cddfa741a099171ad243c6f2f077) Using lowercase keys in bucketResponse struct json ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `fakestorage/response.go` (+2 -2) </details> ### 📄 Description Google Cloud Storage REST APIs use lowercase keys in json bucket response. This will get the fake server to work with the GCS library. Without this `client.list_buckets()` is returning: ``` [<Bucket: None>, <Bucket: None>] ``` with this patch: ``` [<Bucket: another-bucket>, <Bucket: bucket>] ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>