Vue: Ability to pass scoped slots to descedants in templates

[shameleo]

What problem does this feature solve?

The related issue (https://github.com/vuejs/vue/issues/5151) is closed, so I need to clarify my point.

It should exist convenient way to define template for items of hierarchical component (for example, tree or list with sections).
I know, it can be solved with render functions, but it is not so "native" way of building components in vue as in react. I mean, writing / reading render functions is more uncomfortable for average vue user, because they are used only occasionally. It's even worse, if user need to setup webpack / babel / jsx. So I think, render functions should be avoided for not-so-advanced cases.

Slots can be "passed" to children using templates, like this:

<child>
    <template slot-scope="props">
        <slot v-bind="props"></slot>
    </template>
</child>

But there are some drawbacks:
1) This creates wrapper function on each level. First, we have wrapper. Then wrapper of wrapper, and so on.
2) This breaks fallback content (default template) feature.

What does the proposed API look like?

<child>
    <slot slot-scope></slot>
</child>

Remark

I propose syntax, which is boiled down version of first markup, and can be supported by compiler. Here is my test implementation (it seems quite easy): https://github.com/shameleo/vue-slot-pass-demo/commit/bdb6cbbf3ab7574d4b2d350f7d866e2bc609a043
If you give me green light, I'll try to prepare PR. If something is missed in implementation, let me know, please.

[posva]

Hello,
I don't quite understand what you are asking for. If it's about transforming the first version into the second one, you have to know that we prefer not to add more ways of doing already doable things unless the gain justifies it.

[shameleo]

The first version has some drawbacks:

1. This creates wrapper function on each level. First, we have wrapper. Then wrapper of wrapper, and so on.
2. This breaks fallback content (default template) feature.

This is not about just transform.

The first case compiles to this (not actual output, but pseudo to show difference):

render (h) {
  return h('child', {
    scopedSlots: (props) => { return this.$scopedSlots(props) }
  })
}

The second should compile to this:

render (h) {
  return h('child', {
    scopedSlots: this.$scopedSlots
  })
}

[shameleo]

Also note that this

<child>
    <template slot-scope="props">
        <slot v-bind="props"></slot>
    </template>
</child>

and even this

<child>
    <template scope="props">
        <slot :something="props.something"></slot>
    </template>
</child>

does not works in Vue versions prior to 2.5.0, as I found out today. It's just my suggested workaround which works by accident. No guarantee it won't be broken in future versions.

[keithbarrow]

@shameleo - I've just hit the same problem, I think some sort of feature along the lines suggested is an excellent idea. Aside from the (valid) drawbacks you highlight there is the basic problem of having repeated boilerplate, in my case it's down a few generations. Also the current boilerplate _might_ reducing composability, we've several components we're "injecting" via into a common component UI used across projects, even with the current two slots it's ugly.

[yyx990803]

See #7765