Add error handling to getSeekableBlob

[orthatg]

Previously, if getSeekableBlob had any type of error with the fileReader, or with EBML decoding, the error was uncaught and would never proceed to calling the callback.

Now, if it encounters an error, the error is caught and the callback is called with a null result callback(null), allowing the developer's code to respond to the failure instead of halting execution. For example:

getSeekableBlob(blob, myCallback);

function myCallback(result) {
    if (!result) {
        // handle error; alert user that there was a problem
    }
    else {
        // do success handling
    }

Alternatively, making this a Promise and calling reject(error) could be useful, but I felt was out of scope.

[mustafaekim]

I didn't understand how error handling works for this function.

I am getting an error (unrepresentable length ...) on the underlying library (EMBL) but I cannot catch this error. Because I cannot catch, I cannot make the app works in case of error. What can I do ?

[eshajoshi]

Hey @thijstriemstra , are you able to merge this PR into the codebase? Or, is there someone else with write access who are merge this in?

[thijstriemstra]

i'm not a maintainer of this library.

[eshajoshi]

Hey @mustafaekim , are you able to merge this into the codebase?