typing defineComponent props

[Zclhlmgqzc]

Version

3.0.11

Reproduction link

youzan/vant#8701

Steps to reproduce

import { NavBar } from 'vant'
import { defineComponent, h } from 'vue'

export default defineComponent({
  name: 'MyNavBar',
  props: { 
    ...NavBar.props,  
    // more props ...
  }，
  setup(props, { attrs, slots }) {
    return ()  => h(
      NavBar,
      {
        ...props,
        ...attrs
      },
      slots
    )
  }
})

(JSX attribute) title?: string | undefined
<van-nav-bar title={} />

but my-nav-bar title type lost
<my-nav-bar title={} />

What is expected?

(JSX attribute) title?: string | undefined
<my-nav-bar title={} />

What is actually happening?

my-nav-bar title type lost
<my-nav-bar title={} />

[posva]

You might want to open a PR. But you will need to explain yourself (in English) Ines off just post pictures

[Zclhlmgqzc]

@posva I added some background information

[chenjiahan]

@posva @pikax The type of Component.props is missing after wrapping the defineComponent method, which makes it difficult to create HOC.

import { defineComponent } from 'vue';

const Component1 = {
  props: {
    foo: String,
  },
};

const Component2 = defineComponent(Component1);

Component1.props; // --> { foo: StringConstructor }
Component2.props; // --> any

[yyx990803]

#5416 introduced a regression because it changed the argument order of DefineComponent, which breaks component definitions generated via tsc/vue-tsc, and a number of other cases.

We need to find a way to do it while preserving the current argument order of DefineComponent.