timeout setting for Request

[chekoopa]

A simple timeout feature with Maybe field in Request. Test case included. Closes #143.

It was easier than I've thought.

[chekoopa]

Had to force-push twice because of JS formatting fixes. Srry.
But still has strange issues with foreign code, however the test has been successfully completed on the local machine with Spago 0.16.0 and Purs 0.13.8.

[thomashoneyman]

@chekoopa Libraries in the purescript-contrib organization only support ES5 in the FFI to ensure libraries can be used without a bundling step. I'm not sure if that's specifically the error you're seeing, but I do see const and let in there, which will parse with 0.13.8 but isn't ES5.

Do you mind switching over to use ES5 in the FFI file? Most likely that will also resolve the parse issue with the foreign JS as well. In this case it mostly looks like that comes down to swapping var for const / let.

[chekoopa]

@thomashoneyman Sure, done that, let's see what Travis would say.

[thomashoneyman]

Checked the documentation and looks like setting 0 is the correct setting for "no timeout", so the Maybe encoding looks appropriate.

[chekoopa]

Checked the documentation and looks like setting 0 is the correct setting for "no timeout", so the Maybe encoding looks appropriate.

Yes, I've done it first without Maybe, but '0 ms' as a default value may create some misconceptions.

[thomashoneyman]

Thanks @chekoopa. I'd like to give @garyb a chance to take a look, but I think this looks good.

[garyb]

I think this should have been released as a breaking change - adding the field to Request means it will break for anyone who is constructing the value manually rather than overriding defaultRequest.

[thomashoneyman]

🤕 don't release late at night. I've updated the release to be v11.0.0 as this didn't yet make it into Spago and it's only been a few hours.