These are chat archives for ractivejs/ractive

24th
Apr 2017
Chris Reeves
@evs-chris
Apr 24 2017 00:03
Ah, yeah, that would do it
Joseph
@fskreuz
Apr 24 2017 15:02
hey @evs-chris , is ractive.js.org/playground the one in the docs repo or the playground repo?
Chris Reeves
@evs-chris
Apr 24 2017 15:03
yes 😀
The source is in the playground repo, and built files are copied to the docs
Joseph
@fskreuz
Apr 24 2017 15:04
ahh :thumbsup:
paulie4
@paulie4
Apr 24 2017 18:44
It looks like there's another way to reference the root keypath within a template context: {{~/keypath}}, which looks much nicer than {{@.root.data.keypath}}
Chris Reeves
@evs-chris
Apr 24 2017 20:08
That's only for local root, meaning the current component
Chris Reeves
@evs-chris
Apr 24 2017 21:08
Working on some basic material-ish ractive-native components. Anyone interested in checking out the prototype scrollspy decorator? massive playground link
Joseph
@fskreuz
Apr 24 2017 21:15
Nice
Chris Reeves
@evs-chris
Apr 24 2017 21:18
how do you feel about going ahead and breaking the decorator api from decorator(node, ...args) to decorator(contextObj, ...args) where thisremains the ractive instance and ctx.node is the actual node?
the node is useful, but all of my decorators since the context helpers were introduced call this.getNodeInfo(node) as one of the first steps
is it better to break the existing api, or just leave in a tiny bit of boilerplate?
Juan C. Andreu
@andreujuanc
Apr 24 2017 21:36
Hello :shipit:
Ill just be here then x)
I agree that is a bit less struggle to join here
Chris Reeves
@evs-chris
Apr 24 2017 21:40
it also seems to support full gfm, whereas slack is a bit more nebulous on what can be markdowned
Juan C. Andreu
@andreujuanc
Apr 24 2017 21:40
i see some more people as well