-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: Large file upload #302
Comments
Hi, I have taken part in FOSS Hack 2024 and have taken an interest in this issue. My approach for solving this issue would be to use chunked file uploading. Please assign me this issue so that I can start working on it. |
Hey @semi-infiknight sorry for the late reply. you can work on this. i'll give some additional context also, so right now the process of transfering a file to the extension looks like this, hoppscotch website -> hookContent.js -> contentScript -> serviceWorker -> sents the request. the bottleneck is in the contentScript, it uses the there are some paths you could explore to solve this. linking the ongoing discussion about this topic here. there are some workarounds listed there. you'll need to explore these before going the splitting the file and rejoining path. you can use it as a last resort. |
I'm working on this. |
Hey @rifflere , just wanted to check if you're participating in the CodeDay micro-internship program, as issues labeled with |
@SanskritiHarmukh I am working on this issue with my team as past of the CodeDay micro-internship. Sorry for any confusion! |
No worries, assigning the issue to you! |
Is there an existing issue for this?
Summary
When using the chorme extensions proxy to upload files, due to the limitations of the chrome extensions, the file cannot be serialized, which requires a base64 encoding before transferring data through postmessage, resulting in large files being unable to be uploaded and used on the hoppscotch.
Why should this be worked on?
Support for uploading large files on hoppscotch.
The text was updated successfully, but these errors were encountered: