defineComponent (function syntax): optional props inferred as required

[zfeher]

Vue version

3.5.22

Link to minimal reproduction

minimal repro

Steps to reproduce

1, open minimal repo and see the reported error in App.vue at <Comp> usage. It says p1, p2 and p3 required props are missing.

2, open Comp.ts see Comp definition where p1, p2 and p3 are defined as optional props. Hoovering over props in setup func also shows them incorrectly as required.

What is expected?

p1, p2 and p3 props of Comp correctly inferred as optional props like what happens with the similar CompB (options syntax).

What is actually happening?

p1, p2, and p3 props of Comp are inferred incorrectly as required props.

System Info

Any additional comments?

No response

[xiaocainiao633]

CompB: It can be seen that the types of the two are not the same. At this time, TypeScript has inferred it as a required type. TypeScript's function parameter type inference is unidirectional. It cannot "foresee" the type information in the second parameter and apply complex type conversions when parsing the first parameter. Comp: 1.When encountering (props) =>, use the default parameter type inference. 2.Since there is no type information, consider all props as required. 3.By the time the subsequent props options are seen, the previous inference cannot be modified. In CompB: 1.parse the props option. 2.Apply Vue's complex type conversion: ExtractPropTypes + LooseRequired + Readonly. 3.Apply the converted types to the props parameter of the setup function.

[xiaocainiao633]

This comes from the official documentation： defineComoponent

[8797110103-8955]

for Comp can write like this:

import { type ExtractPublicPropTypes } from "vue";

const props = {
      p1: String,
      p2: { type: Number },
      p3: { type: Boolean, required: false },
      p4: { type: String, required: true },
    },
  }
const Comp = defineComponent<ExtractPublicPropTypes<typeof props>>(
  (props) => {
    return () => h('div', 'Comp');
  },
  {
    name: 'Comp1',
    props
);

but, it's too wordy..... has any roadmap by official ???