All Versions
23
Latest Version
Avg Release Cycle
40 days
Latest Release
961 days ago

Changelog History
Page 2

  • v5.5.1 Changes

    February 20, 2020

    [5.5.1] - 2020-02-20

    🛠 Fixed

    • 🛠 Ensure that spaces (url encoded or not) in filenames and paths work as expected when copying (particularly for s3 to s3 native copyObject). Fixes #36.

  • v5.5.0 Changes

    September 09, 2019

    [5.5.0] - 2019-09-09
    ➕ Added
    SFTP backend vfs implementation

  • v5.4.0 Changes

    August 24, 2019

    ➕ Added

    • ➕ Added fallback to TouchCopy for S3/GCS implementations for CopyTo and MoveTo operations between files and locations which use different authentication and region configurations. When possible, the directory copy/move operations will be used by the underlying clients.

  • v5.3.0 Changes

    August 24, 2019

    ➕ Added

  • v5.2.3 Changes

    August 07, 2019

    🛠 Fixed

    • The GS implementation of location.List() returned an empty string for files found inside a persistent "folder" object
      💻 created in the UI or by createing a zero-length object ending with "/". These objects are now ignored.
    • 🛠 Fixed a gs-to-gs copy bug that became visible with integration tests aded in v5.2.2.

  • v5.2.2 Changes

    July 17, 2019

    🛠 Fixed

    • 🚚 The OS implementation of file.MoveToLocation() now ensures that the target directory exists before attempting to move the file

  • v5.2.1 Changes

    July 17, 2019

    [5.2.1] - 2019-07-17

    🛠 Fixed

    • ⚡️ Missing error check in utils.UpdateLastModifiedByMoving()
    • Minor goreportcard checks failed. Now 100%

  • v5.2.0 Changes

    July 16, 2019

    [5.2.0] - 2019-07-16

    ➕ Added

    • In-Memory backend vfs implementation
    • Included the in-memory backend to the list of registered backends used in backend_integration_test
    • 👀 Checking for existence at the start of various File functions (size, seek, etc) and returning and error if the file does not exist on the OS backend
    • Tests in backend_integration_test that ensure that operations done on non-existent files throw an error
    • ⚡️ mem.md in vfs/docs, updated link to it in the README.md

    🛠 Fixed

    • Relative path validation in utils.go now disallows empty names

    🔄 Changed

    • ✅ utils_test.go now expects an empty string NOT to validate
    • ⚡️ updated README to include "Touch()" definition under the File interface rather than the Location interface
    • ⚡️ updated README to exclude "in-memory-backend" from the list of ideas

  • v5.1.0 Changes

    July 08, 2019

    ➕ Added Touch()
    🔨 Refactored for consistency between backends
    ⚡️ Updated docs.
    ➕ Added more tests.
    ➕ Added integration test suite that tests every implementation against interface expectations and against each other.

  • v5.0.0 Changes

    June 18, 2019

    🔄 Changed

    • Defined stricter definitions in interfaces, largely related to input requiements being more URI compliant.
    • FileSystem's NewFile and NewLocation required absolute paths. Locations NewFile and NewLocation require relative paths.
    • ➕ Added/Updated several new utils functions for URI validation across implementations.
    • 🚚 Ensure native methods are being used for atomic functions like copy or move/rename where possible
    • 🚚 Document expected behavior with empty readers in all copy and move function as well as io.Copy
    • ListByPrefix now allows relative paths. ### ➕ Added
    • ✅ Integration test suite for backened developers that ensures expected interface behaviors and tests interactions between implementations.
    • 📄 Examples of io.Copy usage in docs. ### 🛠 Fixed
    • 🛠 Fixed #10
    • 🛠 Fixed vfssimple bug that would return os file system if the uri had the word 'file' anywhere in it even if was s3, like s3://bucket/path/to/file.txt
    • 🛠 Fixed bug where MoveToLocation was returning the old file with updated location rather than a brand new file with new location. Since File may represent a non-existent file, the original file should still be valid.