Marius

Results 69 issues of Marius

See #89 for the underlying discussion. @kvz @janko-m

enhancement
core

Right now, the specification says following about the Tus-Resumable header: > The Tus-Resumable header MUST be included in every request and response except for OPTIONS requests. The value MUST be...

In an unrelated discussion (https://github.com/tus/tus-resumable-upload-protocol/issues/79#issuecomment-225375742), @ruv left an interesting link (https://www.mnot.net/blog/2012/12/04/api-evolution) which drew my attention towards how we address versioning inside the tus protocol. The current state is that we...

core
proposal

For some time, we have had the idea of a separate document containing further explanation about the protocol and best practices for implementations which don't fit into the specification. Here...

- Create a state machine model for tus uploads - Use https://github.com/pfusik/cito to build core logic for tus client - Add JS implementations around core logic to complete tus client

- [ ] Update all dependencies (figure out a solution for packages that do not support CommonJS anymore, e.g. is-stream, into-stream) - [ ] Use async/await inside of many Promises...

Test tus-js-client with large files (multiple GBs), varying browsers, and different options.

enhancement

Consider following code: ```js input.addEventListener("change", function(e) { // Get the selected file from the input element var file = e.target.files[0] // Create a new tus upload var upload = new...

enhancement

tus-js-client might benefit from using TypeScript. In particular, the type safety could be helpful if we want to switch to a state-machine. https://transloadit.slack.com/archives/C02J6C6GQKE/p1656938073529209 provides helpful insights for a tool-assisted switch.

enhancement

Right now, the definitions life in a separate file and have to be updated manually by hand. This sometimes causes the actual interface of tus-js-client and its TS definitions to...

enhancement