These are chat archives for ractivejs/ractive

13th
Jun 2017
kouts
@kouts
Jun 13 2017 06:22
Is there a download link for Ractive 0.9.1? I can only find links for 0.9.0
Joseph
@fskreuz
Jun 13 2017 12:04
Not sure if there's a 0.9.1 officially, but you can always try the edge builds https://cdn.jsdelivr.net/npm/ractive@edge
Juan C. Andreu
@andreujuanc
Jun 13 2017 19:27
ractivejs/ractive#2434
Guys! still no way to do this?
Trevor Morgan
@trvrm
Jun 13 2017 19:31
Is there an explanation somewhere of exactly what Ractive.defaults.isolated does - I'm upgrading my code to 0.9, and I'm not sure I'm understanding it 100%
Chris Reeves
@evs-chris
Jun 13 2017 19:34
@andreujuanc no, but that kinda seems like something that should maybe be possible with a decorator
right now, a decorator only updates if its args change, but there are some cases that have been brought up in the past where it would be useful to know if anything in its context changed
Joseph
@fskreuz
Jun 13 2017 19:36
maybe needs a new lifecycle event, like an onyield or something.
Chris Reeves
@evs-chris
Jun 13 2017 19:36
the best way to do that would be to supply a hook for ractive's internal update mechanism
Joseph
@fskreuz
Jun 13 2017 19:37
Current APIs don't seem to fit the bill (ractive.observe observes data, onupdate observes data, nothing for "on yield dom change")
Chris Reeves
@evs-chris
Jun 13 2017 19:37
I don't think an update event like that would travel well
multiple yields would get pretty confusing, not to mention nested component yields in yields
Joseph
@fskreuz
Jun 13 2017 19:37
yep, that too.
Chris Reeves
@evs-chris
Jun 13 2017 19:38
another decorator hook would be pretty easy to implement though
Trevor Morgan
@trvrm
Jun 13 2017 19:38
Thanks @fskreuz , that's exactly what I was looking for.
Juan C. Andreu
@andreujuanc
Jun 13 2017 19:56
I see
And I agree, i cant see observe on yield
For now I gave my users a datasource which for them does nothing but something to observe xD
I'ts more or less the same scenario as in that github issue.
Needed a drop-in solution
for some Ui migration
Trevor Morgan
@trvrm
Jun 13 2017 20:27

I'm finding that Ractive plugins aren't really keeping up with the changes in the core repo. E.g. in upgrading to 0.9, I found that the ractive-load plugin stopped working. (Because it makes a call to Ractive.Promise, which doesn't exist any more.)

Are those dead projects, or should I try and get patches submitted to them?

Joseph
@fskreuz
Jun 13 2017 20:27
The really long thread about that is ractivejs/ractive#2271
The conclusion (the last comment) was to revamp the docs first.
kouts
@kouts
Jun 13 2017 20:30
@trvrm maybe Ractive.Promise = Promise; helps?
Trevor Morgan
@trvrm
Jun 13 2017 20:30
Ah, right, yes, I could just hack my way around the problem for now. Thanks!
Joseph
@fskreuz
Jun 13 2017 20:33
I'm aiming on updating plugins as soon as the docs get polished up. So they're not totally left behind.
Trevor Morgan
@trvrm
Jun 13 2017 20:33
That worked perfectly, thanks @kouts !
kouts
@kouts
Jun 13 2017 20:38
:thumbsup:
the solution to transitions is already a work in progress, apparently
Joseph
@fskreuz
Jun 13 2017 22:22
oooh :thumbsup: