Removes axios, replacing it with fetch. Also adds a new withHttpOptions() method to DirectBinaryUploadOptions, and removes several methods that are rendered obsolete by withHttpOptions().
PR also includes an upgrade guide, which will be required due to the breaking changes it introduces.
Related Issue
106
Motivation and Context
We want to increase the library's flexibility by allowing consumers to have increase control over the options that are used when making HTTP requests. This was difficult because aem-upload uses axios when creating directories, but node-httptransfer uses fetch when uploading files. By bringing the two inline, we can now add a single withHttpOptions() method that will allow consumers to provide whichever options they want for fetch.
How Has This Been Tested?
Manual local testing by uploading files and folders, then verifying the results. e2e tests and unit tests all pass.
Screenshots (if appropriate):
N/A
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
Description
Removes
axios
, replacing it withfetch
. Also adds a newwithHttpOptions()
method toDirectBinaryUploadOptions
, and removes several methods that are rendered obsolete bywithHttpOptions()
.PR also includes an upgrade guide, which will be required due to the breaking changes it introduces.
Related Issue
106
Motivation and Context
We want to increase the library's flexibility by allowing consumers to have increase control over the options that are used when making HTTP requests. This was difficult because
aem-upload
usesaxios
when creating directories, butnode-httptransfer
usesfetch
when uploading files. By bringing the two inline, we can now add a singlewithHttpOptions()
method that will allow consumers to provide whichever options they want for fetch.How Has This Been Tested?
Manual local testing by uploading files and folders, then verifying the results. e2e tests and unit tests all pass.
Screenshots (if appropriate):
N/A
Types of changes
Checklist: