-
Notifications
You must be signed in to change notification settings - Fork 959
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
Not displaying max_entries error when multiple uploads #2835
Comments
I am almost sure this change was intentional. Otherwise, if the user wants to add new files, they need to remove the old ones, and select new ones, even when it is clear the old ones won't upload. And this makes the flow very annoying for auto-uploads, especially when drag and drop is enabled. |
I'm not sure I understand. It doesn't display the error for the failed uploads so how would the user know there is a problem? |
It will display once you have more than max_entries succeed. |
But that isn't possible because they just sit in the pending upload column (2 will be in completed) 1 will be in pending with no error |
Oh, I see. It is failing because it is too many entries, not because of other reasons! |
Fixes phoenixframework#3115. Relates to phoenixframework#3004. Partially fixes phoenixframework#2835.
Fixes phoenixframework#3115. Relates to phoenixframework#3004. Partially fixes phoenixframework#2835.
Related to #2807. I think the problem is that since that change we auto upload up to max_entries even if more than max_entries are submitted. After the auto upload the too many files error is removed in recalculate_errors. So either we don't auto upload in that case or we keep the too many files error in case of auto uploads? |
Environment
Actual behavior
https://gist.github.com/dankentfield/719666ede4370ab7a9a6c511a82b0983
Expected behavior
The text was updated successfully, but these errors were encountered: