Not sure who worked on the new update, but it’s awesome.
Better padding and line-height for text, shiny buttons, and smooth fading tooltips =
Great job!
Not sure who worked on the new update, but it’s awesome.
Better padding and line-height for text, shiny buttons, and smooth fading tooltips =
Great job!
I don’t remember any work done to Crystal Playground.
Do you mean the thing that pops up when you run crystal play
, or play.crystal-lang.org
? (in any case I don’t see any change, but then I have bad memory)
Are you talking about https://code.labstack.com/crystal?
Nah, https://play.crystal-lang.org
It looks way cleaner than before. Whoever changed it, it is deeply appreciated (I use it soooo much)
Yeah, that was updated.
Commit: https://github.com/jhass/carc.in/commit/90f490f2fdeaf8303792711a6a632f091c97e96e
I actually no longer see how to compile and run code there:
I mean, the interface looks a little slicker, to be sure, but I’m currently totally unable to use it (both on play.crystal-lang.org and on carc.in).
Edit: The interface appears when I refresh the page (but not the first time I navigate to it).
Yeah, I’ve noticed that as well. I tried a hard reload, and it’s still happening, weird. Console shows:
vendor-fd3b6e051b057eda03550a10f8ddf786.js:250 jQuery.Deferred exception: Cannot read property 'filter' of undefined TypeError: Cannot read property 'filter' of undefined
at r.updateVersions (https://play.crystal-lang.org/assets/carcin-c82300b955d2f980cb02ca14bf6893ed.js:17:142)
at r.didReceiveAttrs (https://play.crystal-lang.org/assets/carcin-c82300b955d2f980cb02ca14bf6893ed.js:15:44)
at r.trigger (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:2510:34)
at r [as trigger] (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:2365:9)
at n.i.create (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:966:45)
at Object.evaluate (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:3438:9)
at e.t.evaluate (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:3292:13)
at e.t.evaluateSyscall (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:3628:73)
at e.t.evaluateInner (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:3620:158)
at e.t.evaluateOuter (https://play.crystal-lang.org/assets/vendor-fd3b6e051b057eda03550a10f8ddf786.js:3620:67) undefined
_.Deferred.exceptionHook @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:250
c @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:242
setTimeout (async)
(anonymous) @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:243
l @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:234
fireWith @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:235
fire @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:235
l @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:234
fireWith @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:235
ready @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:252
U @ vendor-fd3b6e051b057eda03550a10f8ddf786.js:252
vendor-fd3b6e051b057eda03550a10f8ddf786.js:250 Uncaught TypeError: Cannot read property 'filter' of undefined
at r.updateVersions (carcin-c82300b955d2f980cb02ca14bf6893ed.js:17)
at r.didReceiveAttrs (carcin-c82300b955d2f980cb02ca14bf6893ed.js:15)
at r.trigger (vendor-fd3b6e051b057eda03550a10f8ddf786.js:2510)
at r [as trigger] (vendor-fd3b6e051b057eda03550a10f8ddf786.js:2365)
at n.i.create (vendor-fd3b6e051b057eda03550a10f8ddf786.js:966)
at Object.evaluate (vendor-fd3b6e051b057eda03550a10f8ddf786.js:3438)
at e.t.evaluate (vendor-fd3b6e051b057eda03550a10f8ddf786.js:3292)
at e.t.evaluateSyscall (vendor-fd3b6e051b057eda03550a10f8ddf786.js:3628)
at e.t.evaluateInner (vendor-fd3b6e051b057eda03550a10f8ddf786.js:3620)
at e.t.evaluateOuter (vendor-fd3b6e051b057eda03550a10f8ddf786.js:3620)
On the first load. Then when you refresh, the error is gone. This might help @jhass
Same for me. I loaded it, it only showed the editor, then reloaded it, it was fine.
Also, I haven’t even used Crystal playground on this device yet, so it must be on the first load of the new update (maybe some caching issue? )
/cc @jhass
Sorry folks, hopefully fixed now :)
Seems to be fixed now!