Size Report

Bundles

Usages

Based on the comment on h.ts

/*
// type only
h('div')

// type + props
h('div', {})

// type + omit props + children
// Omit props does NOT support named slots
h('div', []) // array
h('div', 'foo') // text
h('div', h('br')) // vnode
h(Component, () => {}) // default slot

// type + props + children
h('div', {}, []) // array
h('div', {}, 'foo') // text
h('div', {}, h('br')) // vnode
h(Component, {}, () => {}) // default slot
h(Component, {}, {}) // named slots

// named slots without props requires explicit `null` to avoid ambiguity
h(Component, null, {})
**/

This is working as intended, this PR is requesting to change the API.

The only case where we could argue otherwise would be Teleport not supporting the function.

If the intention is for functions to be supported across the board h.ts needs to be updated

@pikax
I believe we should offer comprehensive support for this, so that we can pass a function in situations where it's uncertain whether tag represents a component or an HTMLElement:

let tag: string | Component = 'div'

h(tag, {}, () => 'hello world')

If we only support Component, the above use case would result in the loss of child elements when dealing with HTMLElement or Teleport

I believe we should offer comprehensive support for this, so that we can pass a function in situations where it's uncertain whether tag represents a component or an HTMLElement:

I'm not saying otherwise, just saying this is a change of the current API, changing API is more cumbersome, there's typescript that needs to be updated which this PR hasn't done it, there's RFC.

I would argue logically it makes sense why Element to not support functions, the reason I say that is because functions are a sugar for default slot, but Element doesn't have slots per se, is just children, because slots implies a vue component.

@pikax I see there are overloads for Teleport here.