Browser File support?

[jrobinso]

Thoughts on supporting the browser File object? If you're not working on it, I might take a crack at it. It should be pretty simple, I think we need to implement an "io" file class for it, then some conditional logic to prevent the app from blowing up if run in node.

[rbuels]

That would be great, perhaps a PR with a io/browserFile.js?

…

On Wed, Jan 16, 2019 at 8:50 PM Jim Robinson ***@***.***> wrote: Thoughts on supporting the browser File object? If you're not working on it, I might take a crack at it. It should be pretty simple, I think we need to implement an "io" file class for it, then some conditional logic to prevent the app from blowing up if run in node. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEgFe3jpP-9X2zKe_v3qnxBp1ZWpZ7Kks5vEAEYgaJpZM4aEdIW> .

[jrobinso]

@rbuels That was my plan, but @cmdcolin pointed to using the fileHandle option and supplying an implementation from outside. That might make more sense, and leaving cram-js a pure node application.

[jrobinso]

@rbuels @cmdcolin Perhaps we could put an implementation of filehandle (for args.filehandel) for the browser File object as an example file somewhere for other people to copy and use. This keeps cram-js pure node. When I have one I'll let you know.