Closed SgtPooki closed 8 months ago
On mobile but wanted to give a shout that ive got a refactor going that cleans this up a bunch
ive got a refactor going that cleans this up a bunch
Done a first pass, will look again after the refactor lands.
FYI: some tests were failing when merging main into byte-range PR due to new ipns things. changes at acdd632
(#10)
commenting elsewhere since the thread (https://github.com/ipfs/helia-verified-fetch/pull/10#discussion_r1521644018) was collapsed:
we could solve both concerns by setting internalFileSize so we know which value we set vs consumers.. but that could get confusing. i'll leave as is for now.
i've got _isRangeRequest updated locally, and have isValidRangeRequest updated as well.
So now we have:
inaccessable properties outside the ByteRangeContext class:
_fileSize
// 8837738
(#10)_contentRangeHeaderValue
// getter (depends on other operations)314adca
(#10)_body
// set/get methods_isValidRangeRequest
// getter (depends on other operations)d633456
(#10)the only outlier here seems to be _body having setBody
and getBody
methods
:tada: This PR is included in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.7.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Title
Add Range header support.
Description
Fixes https://github.com/ipfs/helia-verified-fetch/issues/9
Notes & open questions
handling ReadableStreams
tests, but these are covered byrange requests
tests.. going to try to fix quickly and if I can't i'll remove them.Change checklist