Repository navigation
Open
Labels
Area: APIsThings related to external and internal APIsThings related to external and internal APIsPriority: MediumThis issue may be useful, and needs some attention.This issue may be useful, and needs some attention.Status: AcceptedIt's clear what the subject of the issue is about, and what the resolution should be.It's clear what the subject of the issue is about, and what the resolution should be.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Description
Support plan
- 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): somehow
Context
- Node.js version: 21.6.2
- Release Line of Formidable (Legacy, Current, Next): latest
- Formidable exact version: latest
- Environment (node, browser, native, OS): node
- Used with (popular names of modules): idk
What are you trying to achieve or the steps to reproduce?
I think the maxFileSize check only happens after the file is fully uploaded, how to make it so it's immediate after bytes received exceed the set limit?
What was the result you got?
Only after file fully uploaded
What result did you expect?
Immediately after limit is reached
Metadata
Metadata
Assignees
Labels
Area: APIsThings related to external and internal APIsThings related to external and internal APIsPriority: MediumThis issue may be useful, and needs some attention.This issue may be useful, and needs some attention.Status: AcceptedIt's clear what the subject of the issue is about, and what the resolution should be.It's clear what the subject of the issue is about, and what the resolution should be.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Inconsistencies or issues which will cause an issue or problem for users or implementors.
Activity
tunnckoCore commentedon Mar 10, 2024
I think so too. But I thinko you can work around that by using
onPart