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
Which support plan is this issue covered by? (Community, Sponsor, Enterprise): Community
Currently blocking your project/work? (yes/no): yes
Affecting a production system? (yes/no): yes
Context
Node.js version: 16.13.2
Release Line of Formidable (Legacy, Current, Next):
Formidable exact version: 2.0.1
Environment (node, browser, native, OS): node
Used with (popular names of modules): aws-sdk, next, PassThrough
What are you trying to achieve or the steps to reproduce?
I am passing a fileWriteStreamHandler function to handle uploads to s3. This sends a passthrough stream to s3, and sets up a callback that runs after the upload has finished. This callback contains any errors that occured during the upload process. Throwing any errors that are defined in this callback falls outside of the scope of form.parse and the 'error' event. In fact, the 'end' event fires before this callback even runs. How are these errors supposed to be handled within the same scope as the form processing/parsing?
What was the result you got? As stated above, throwing an error from within the callback defined in the fileWriteStreamHandler is outside the scope of formidable. This presents an error handling challenge.
What result did you expect? I would expect all errors related form parsing/processing to have a common scope within which they can be handled. This currently does not seem to be the case
The text was updated successfully, but these errors were encountered:
Support plan
Context
What are you trying to achieve or the steps to reproduce?
I am passing a fileWriteStreamHandler function to handle uploads to s3. This sends a passthrough stream to s3, and sets up a callback that runs after the upload has finished. This callback contains any errors that occured during the upload process. Throwing any errors that are defined in this callback falls outside of the scope of form.parse and the 'error' event. In fact, the 'end' event fires before this callback even runs. How are these errors supposed to be handled within the same scope as the form processing/parsing?
What was the result you got? As stated above, throwing an error from within the callback defined in the fileWriteStreamHandler is outside the scope of formidable. This presents an error handling challenge.
What result did you expect? I would expect all errors related form parsing/processing to have a common scope within which they can be handled. This currently does not seem to be the case
The text was updated successfully, but these errors were encountered: