You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: update dependencies
- Update uuid to ^11.1.0 and add @types/uuid
- Update @autonomys/file-caching to ^1.5.1
- Update related dependencies across packages
* feat: add HTTP range request utility functions
- Add parseByteRange function for parsing Range headers
- Add createPartialStream function for creating range-aware streams
- Add utility functions for handling HTTP 206 partial content responses
- Support for byte-range requests in readable streams
* feat: implement range request support in download services
- Add ByteRange interface for range request parameters
- Implement partial download support in memory cache
- Add range-aware download methods in download service
- Support for caching partial content with byte ranges
- Add sync download functionality with range support
* feat: add HTTP range request support to download controllers
- Update download controller to handle Range headers
- Implement HTTP 206 Partial Content responses
- Add proper Content-Range and Accept-Ranges headers
- Support partial file downloads in object controllers
- Update use cases to handle byte range parameters
- Add range request support to object download endpoints
* test: add comprehensive tests for partial retrieval functionality
- Add tests for byte range parsing and validation
- Test partial content download scenarios
- Verify HTTP 206 response handling
- Add test cases for range request edge cases
- Test memory cache integration with range requests
* refactor: move to separate files related logic
* refactor: enhance download response handling with byte range support
- Introduced isExpectedDocument function to streamline document expectation checks
- Refactored handleDownloadResponseHeaders to utilize setFileResponseHeaders and setFolderResponseHeaders for improved clarity
- Added byte range handling in setFileResponseHeaders for partial content responses
- Updated content disposition and content type settings based on encryption and document expectations
* refactor: reorganize file use cases
* fix(testing): cache populated in async setting
* feat: update auto files gateway version
* update: bump auto-sdk version
* refactor: update FilesUseCases tests and imports
- Refactored tests for FilesUseCases to use getObjectInformation instead of getMetadata.
- Updated mock implementations to reflect changes in the download blocking logic.
- Cleaned up imports in files.spec.ts and index.ts for better organization and clarity.
* refactor: clean up imports in files.spec.ts
- Removed unused dbMigration import to streamline the test file and improve clarity.
* fix: update byte range header handling in getByteRange function
- Changed the header used to retrieve the byte range from 'content-range' to 'range' for improved accuracy in handling byte range requests.
* fix: enhance byte range validation in getByteRange function
- Added validation checks to ensure start and end byte values are non-negative and that the start value does not exceed the end value, improving the robustness of byte range handling.
* chore: update package dependencies to version 1.5.11
* chore: update yarn.lock to reflect package versions 1.5.11 for auto-dag-data and file-caching
0 commit comments