Fix For When user selects Empty files using File Upload

[Yummy-Yums]

All Submissions:

• Have you followed the guidelines stated in CONTRIBUTING.md file?
• Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

New Feature Submission:

• Does your submission pass the tests?
• Have you linted your code locally prior to submission?

Changes To Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.

a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

[Yummy-Yums]

#2873

[masenf]

the payload is supposed to be a object, not an array

[Yummy-Yums]

you mean return await applyEvent(Event(event.name, event.payload), socket)

[masenf]

the problem is that event.payload contains keys that do not map to an arbitrary event handler on the backend.

for example, maybe it works if the backend event handler has a files arg; but if that arg is named fools, then we get an error on the backend about unknown keyword argument.

[masenf]

what is this change doing? if we end up hitting this code, won't it ultimately throw that "Did not find CR at end of boundary (40)" error in the upload handler?

[Yummy-Yums]

correct, resolved it

[masenf]

the only thing that still makes me nervous about this is that, if the handler doesn't specify a default for the list[rx.UploadFile] arg, then there will be a traceback printed on the backend, whereas before, this was just a no op.

i think that's okay though. it will still be a no-op, and if they want to avoid the traceback, they can add a default value...

[Yummy-Yums]

the only thing that still makes me nervous about this is that, if the handler doesn't specify a default for the list[rx.UploadFile] arg, then there will be a traceback printed on the backend, whereas before, this was just a no op.

i think that's okay though. it will still be a no-op, and if they want to avoid the traceback, they can add a default value...

i think we can put it in a doc somewhere ? or leave it like that? what dyu suggest ?