Hi Nige,

looks very nice so far. The only thing I am wondering about: do we really want to push the cors dependency into the repo? Not really needed there. Also, the app.js file on top level. Guess we could move that one into the example folder and maybe rename it into server (with a comment that it requires express & cors). Thoughts?

That's why this is a Draft PR. I'm not suggesting that stuff be kept in.

It's for discussion and the sharing of code at this stage.

We will have to work out a testing strategy separately. The sequences of interactions and the states cycled through are complex, so it will need a test, and that will need some HTTP server which will produce known results in a similar way to that little Express server.

This is the example page, which by going to server endpoints with known responses, exercises all the states. The example may finish with the four possible stable states when a file is selected in each one.

• Successful upload and scan and downloadable
• Successful upload and scan and not downloadable
• Failed upload
• Failed malware scan

From these states, clicking that action icon will reset the widget to its ready state.

closing the draft PR & creating a real one