Event handlers in each block don't work.

[dxlbnl]

{{#each items as item}}
    <Component on:change="method(item, event)" />
{{/each}}

Turns in to this code:

function renderEachBlock ( root, eachBlock_value, slider, slider__index, component ) {
// ...
component1.on( 'change', function ( event ) {
    var eachBlock_value = this.__svelte.eachBlock_value, component__index =  this.__svelte.component__index, slider = eachBlock_value[component__index];
    component.method(item, event);
});

But this.__svelte doesn't exist. So the handler can't be called.

[Rich-Harris]

Ah, yeah — it's treating the component the same as it would treat a DOM node, which is incorrect. Thanks for flagging it.

[cristinecula]

A simple workaround I use is omitting the iterated value from the event handler and sending it as the event:

{{#each items as item}}
    <Component item={{item}} on:change="method(event)" />
{{/each}}

<span on:click="fire( 'change', item )">{{ item.name }}</span>

[dxlbnl]

@Rich-Harris Ah, so that's going on, I was thinking __svelte might be some legacy or something. But it was used too often in the codebase :).

Another question, it isn't possible to make dynamic value:binds right? as in, take a propertypath, and bind that path to the component.

i.e.:

{{#each boundProps as prop}}
  <Component bind:value="{{prop}}" />
{{/each}}

The reason I stumbled onto this bug was because I want to dynamically generate the components, based on a simple data structure.
Now, mapping the values back up the component hierarchy would require a event chain (i think)

@cristinecula Thanks for the advice, I might look into this, although it would leak a bit too much to Component for my taste ;)

[Rich-Harris]

Svelte does map values back up the data hierarchy (gist, demo), but it doesn't work with components — you've discovered another bug!

[Rich-Harris]

Both these bugs are now fixed — closing this issue