These are chat archives for ractivejs/ractive

15th
Feb 2018
Simon Layfield
@simonlayfield
Feb 15 2018 10:43
@PaulMaly_twitter Hey, sorry - I completely neglected to say thanks for your previous feedback on my component efforts. Really appreciate it - also to others who chimed in.
Joseph
@fskreuz
Feb 15 2018 11:23
@evs-chris In a component file, in what cases is a partial element (<template id="somepartialname">) preferrable over an in-template partial ({{#partial somepartialname }})? Just wondering why it has to be separate when it can ride along and be parsed together with the template.

i.e Why this:

<template>
  {{ msg }} {{> somepartial}}
</template>

<template id="somepartial">
  {{ anothermsg }}
</template>

over this:

<template>
  {{ msg }} {{> somepartial}}

  {{#partial somepartial }}
    {{ anothermsg }}
  {{/partial}}
</template>
Chris Reeves
@evs-chris
Feb 15 2018 15:26
for the bin? it's just easier for me to read the tag version
there's also non-top-level inline partials that behave differently
Joseph
@fskreuz
Feb 15 2018 15:55
Ah, right. Partials get scoped to the nearest containing element.
So it's more for readabililty, which makes sense. I love code folding. :D
Chris Reeves
@evs-chris
Feb 15 2018 16:00
now that the template element is a thing, it might make sense to swap out inline partials, which are a bit hard to read, with inline template tags
similar for slots
Joseph
@fskreuz
Feb 15 2018 23:23
#TodayILearned Buble's repl... uses Ractive :tada: https://buble.surge.sh
Martin Kolárik
@MartinKolarik
Feb 15 2018 23:30
would be more interesting if svelte's repl used Ractive :laughing:
Chris Reeves
@evs-chris
Feb 15 2018 23:49
😂