Fixed no response return onload callback

[Yahasana]

If there is nothing return from onload callback, use xhr.response by default

[rikschennink]

There is no related issue. This is also not a bug. Please in future first submit issue with bug report then we can discuss a PR.

[Yahasana]

It's not a bug, but it's a bad implement. It's take me a whole day to investigate what the hell of failing revert upload. e.g.

FilePond.setOptions({
    server: {
        process: {
            method: "POST",
            onload: (response) => {
                console.log(response)
                // return response  <-- revert upload by serverId rely on this return! wtf
            }
    }
})

[rikschennink]

I'm not comfortable changing this behaviour at this point in time. If you set onload you need to return a value.

This will go wrong when dev returns 0 or false or another falsy value in the onload hook.

onload(xhr.response) || xhr.response,

[rikschennink]

Will re-open, PR should be updated to fix above issue with falsy values.

[Yahasana]

why people returns 0 or false as keyId? bad practice it's

[rikschennink]

@Yahasana file server id could potentially 0