<GitHub11>
[opal-jquery] adambeynon pushed 1 new commit to master: http://git.io/-yVogQ
<GitHub11>
opal-jquery/master 2b3dded Adam Beynon: Make Element#[] return nil for empty attributes #39
GitHub11 has left #opal [#opal]
Helios__ has joined #opal
<Helios__>
hello everyone
<Helios__>
I would like to know how to compile an entire Ruby Gem into javascript, is that possible ?
GitHub47 has joined #opal
<GitHub47>
[opal-jquery] adambeynon closed pull request #35: Let Element#to_s behave the same as Element#inspect (master...master) http://git.io/2IevDg
GitHub47 has left #opal [#opal]
GitHub100 has joined #opal
<GitHub100>
[opal-jquery] adambeynon pushed 5 new commits to master: http://git.io/wObpzA
<GitHub100>
opal-jquery/master e2ea2e0 Roy van der Meij: Element#to_s gave an <Element: Undefined> while Element#inspect gave a better output like <Element: [div id="some_div"]>
<GitHub100>
opal-jquery/master 45f0ee0 Roy van der Meij: don't check for document but check if tagName exists
<GitHub100>
opal-jquery/master 9cac3cb Roy van der Meij: alias to_s to inspect as it does exactly the same
GitHub100 has left #opal [#opal]
GitHub58 has joined #opal
<GitHub58>
[opal-jquery] adambeynon pushed 1 new commit to master: http://git.io/AixtBw
<GitHub58>
opal-jquery/master 69364dc Adam Beynon: Update some spec styling
GitHub58 has left #opal [#opal]
e_dub has quit [Quit: ZZZzzz…]
e_dub has joined #opal
wmnnd has quit [Ping timeout: 272 seconds]
Helios__ has quit [Ping timeout: 246 seconds]
wmnnd has joined #opal
GitHub117 has joined #opal
<GitHub117>
[opal-jquery] adambeynon pushed 2 new commits to master: http://git.io/OPpgHA
<GitHub117>
opal-jquery/master 67034c4 Adam Beynon: Move rspec helpers into opal/ for other libs to use
<GitHub117>
opal-jquery/master 95a9e84 Adam Beynon: Some spec tidying
GitHub117 has left #opal [#opal]
e_dub has quit [Quit: ZZZzzz…]
GitHub84 has joined #opal
<GitHub84>
[opal] adambeynon pushed 1 new commit to master: http://git.io/sVZQUw
<GitHub84>
opal/master f151e85 Adam Beynon: Fixes for Enumerator#with_index #550
GitHub84 has left #opal [#opal]
travis-ci has joined #opal
<travis-ci>
opal/opal#2095 (master - f151e85 : Adam Beynon): The build passed.
<GitHub135>
[opalrb.org] adambeynon pushed 1 new commit to master: http://git.io/0KUS6A
<GitHub135>
opalrb.org/master ae83c26 Adam Beynon: Initial unsupported_features document
GitHub135 has left #opal [#opal]
GitHub117 has joined #opal
<GitHub117>
[opalrb.org] adambeynon pushed 1 new commit to gh-pages: http://git.io/4G3-jg
<GitHub117>
opalrb.org/gh-pages e66b83d Adam Beynon: Site updated to ae83c26
GitHub117 has left #opal [#opal]
ryanstout has joined #opal
noomerikal has joined #opal
meh` has joined #opal
ylluminarious has joined #opal
<ryanstout>
adambeynon: did you figure out the issue with promises?
<ryanstout>
the one I was having before was just me missing the obvious (passing a block without calling .then)
<ryanstout>
but now I’ve got one where it doesn’t run until I add a .fail (even though I’m resolving it)
ylluminarious has quit [Client Quit]
<ryanstout>
it might be that I’m calling it on wrong thing though
<ryanstout>
ok, looks like it has something to do with calling return in a then block
<ryanstout>
(I should say I’m running promise.rb with opal and mri)
<adambeynon>
ryanstout: I'll have a look. Promise was done by meh` so he might know a bit more about its quirks...
<ryanstout>
meh`: you around?
<ryanstout>
adambeynon: thanks, I’m digging through it at the moment.
<ryanstout>
it’s weird a return would make a difference
<ryanstout>
oh, sorry, I’m dumb
<ryanstout>
it’s because it was getting chained on and returning doesn’t return the promise
<ryanstout>
ok, sorry, nevermind
<ryanstout>
my bad
<adambeynon>
Agh, return inside a block?
<ryanstout>
yea
<ryanstout>
I was just missing the obvious
<ryanstout>
actually, this might be a common issue with Promises
<ryanstout>
(in that I probably won’t be the only one to make this mistake)
<ryanstout>
maybe there should be a lambda wrapping the then block or something so returns don’t leak out
<ryanstout>
since promises are all about chaining and return breaks the chain and causes them to never get run in some cases
<meh`>
ryanstout, yes
<ryanstout>
sorry, actually nevermind for now. Was having an issue, but it was on my end. Thanks
<wmnnd>
I am getting a really strange exception, maybe one of you has an idea what could be the reason for it. I have a method with an each-loop that returns an element from an array if certain conditions are met. Neither Firefox nor Chromium complain (i.e. log exceptions).
<ryanstout>
meh`: on promises, what’s the difference between resolve and resolve!
<meh`>
ryanstout, you shouldn't call resolve!
<wmnnd>
However, if I enable "pause on exceptions", Firefox does give me an error while Chromium doesn't. Unfortunately, the error has no error description, it is just an "error" that eventually makes the script stop at "throw Opal.returner"
<meh`>
ryanstout, resolve! is internal
<ryanstout>
ok, cool
<meh`>
like all the << >> ^ plumbing
e_dub has joined #opal
<ryanstout>
meh`: what does ‘always’ do? Haven’t seen that one before
<wmnnd>
The line in which it fails is a simple "return" call. It doesn't matter if I return an Object or simply true or a number.
<meh`>
ryanstout, it catches both resolves and rejects
<ryanstout>
ok
<meh`>
ryanstout, it's like an ensure
<ryanstout>
cool
e_dub has quit [Quit: ZZZzzz…]
<wmnnd>
Ah, I see. Opal uses exceptions for the return statement so that you will get stuck in debugging limbo if you don't tick "Ignore caught exceptions" ^_^