<adambeynon>
morning elia. Have you used promises from stdlib?
<adambeynon>
or, promises in general really
<adambeynon>
Basically, when a then() block fails, unless I define a rescue() block, it feels like errors are being swallowed up, but I find it irritating to keep adding a rescue block just to debug the odd error
<adambeynon>
I was thinking of adding a Promise.on_error() handler that would be passed every failure, even if it does get handled in the rescue() blocks
<adambeynon>
could use that then to simply print errors to stdout
<adambeynon>
perhaps more of a question for meh, as he wrote it
<elia>
][
<elia>
adambeynon, yeah, not really experienced with promises
<elia>
adambeynon, btw did the beta worked well on your projects? maybe it's time to release :)
<adambeynon>
elia: I was thinking the same
<adambeynon>
and yes it does
<adambeynon>
works like a charm
<adambeynon>
should I spend a few hours going through the website to make sure the docs are up to date first?
<adambeynon>
there are probably subtle differences for the sinatra stuff, for example
<adambeynon>
also, now we have gone through the hard work, and done all the major changes, I really want to push out bumped version as often as possible
<adambeynon>
not a fan of huge gaps between releases
<ryanstout>
adambeynon: I saw you were having some errors swallowed with promises. I think I’m seeing something similar. Though for me it’s not errors, it’s that in some weird case it doesn’t chain .then’s
<ryanstout>
I’m still trying to figure it out
<adambeynon>
meh`: did you catch that conversation earlier? Basically, if I have a chain of promises, and then an error happens somewhere in all the callbacks, then unless I use a #rescue() block, the error just gets swallowed up. Instead of having a rescue block all over the place, which would be used just during development, I was wonder whether we could introduce some
<adambeynon>
global error handler which can be used to log any promises that error
j_mcnally has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
j_mcnally has joined #opal
j_mcnally has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
elia has quit [Quit: Connection closed for inactivity]
e_dub has quit [Quit: ZZZzzz…]
e_dub has joined #opal
GitHub176 has joined #opal
<GitHub176>
[opalrb.org] jaredcwhite opened pull request #8: Improve the documentation for using Ruby/Opal objects from Javascript (master...master) http://git.io/5uABiw
GitHub176 has left #opal [#opal]
fkchang has joined #opal
e_dub has quit [Quit: ZZZzzz…]
GitHub38 has joined #opal
<GitHub38>
[opalrb.org] adambeynon pushed 1 new commit to master: http://git.io/Xd_24Q
<GitHub38>
opalrb.org/master 9c2392c Adam Beynon: Some site cleanup
GitHub38 has left #opal [#opal]
GitHub146 has joined #opal
<GitHub146>
[opalrb.org] adambeynon pushed 1 new commit to gh-pages: http://git.io/rGGQaw
<GitHub146>
opalrb.org/gh-pages dead09e Adam Beynon: Site updated to 9c2392c
GitHub146 has left #opal [#opal]
GitHub43 has joined #opal
<GitHub43>
[opalrb.org] adambeynon closed pull request #8: Improve the documentation for using Ruby/Opal objects from Javascript (master...master) http://git.io/5uABiw
GitHub43 has left #opal [#opal]
GitHub117 has joined #opal
<GitHub117>
opalrb.org/master 973ac3d Jared White: Add extra note about using bracket notation...
<GitHub117>
opalrb.org/master ccdbd75 Jared White: Add section about interacting with a Hash from Javascript
<GitHub117>
opalrb.org/master 0448393 Adam Beynon: Merge pull request #8 from jaredcwhite/master...
GitHub117 has left #opal [#opal]
<GitHub117>
[opalrb.org] adambeynon pushed 3 new commits to master: http://git.io/2g07Lg