v1.47.0

Release v1.47.0

✨ Features

🔹 GCS File System Integration

Introduced Google Cloud Storage (GCS) File System as a new implementation of the GoFr FileSystem interface. This enables seamless integration with GCS while maintaining consistent behavior across existing backends like S3, FTP, and SFTP.

Supported Methods:

type FileSystem interface {
    Create(name string) (File, error)
    Mkdir(name string, perm os.FileMode) error
    MkdirAll(path string, perm os.FileMode) error
    Open(name string) (File, error)
    OpenFile(name string, flag int, perm os.FileMode) (File, error)
    Remove(name string) error
    RemoveAll(path string) error
    Rename(oldname string, newname string) error
    ReadDir(dir string) ([]FileInfo, error)
    Stat(name string) (FileInfo, error)
    ChDir(dirname string) error
    Getwd() (string, error)
}

• Consistent and unified interface for GCS, S3, FTP, and SFTP file operations.
• Plug-and-play compatibility with GoFr’s file abstraction layer.
• Production-ready with proper error wrapping, retries, and structured logging.
• Simplifies backend switching without changing application logic.

For detailed usage, visit 👉 GoFr Docs — GCS File System

---

🛠️ Bug Fixes

Remote Logger — Improper JSON Log Formatting

Previously, ANSI color codes and non-ASCII characters appeared in JSON logs, breaking downstream log parsers.

Example of affected log output:

{"level":"DEBUG","time":"2025-09-17T17:54:30.625115633Z","message":"\u001b[38;5;8m5460fd91feac021fd633b5989abdeb26 \u001b[38;5;34m200   \u001b[0m     5855\u001b[38;5;8mµs\u001b[0m GET https://myurl","gofrVersion":"v1.45.0"}

Fix Summary:

• Removed ANSI color codes and non-ASCII characters from JSON logs.
• Preserved terminal log colors for local debugging.
• Ensured all remote JSON logs are now ASCII-safe and parseable by log processors (ELK, Loki, Cloud Logging, etc.).