`vue/require-default-prop` doesn't trigger with props destructure

[hartbit]

Checklist

• I have tried restarting my IDE and the issue persists.
• I have read the FAQ and my problem is not listed.

Tell us about your environment

• ESLint version: 9.21.0
• eslint-plugin-vue version: 10.0.0
• Vue version: 3.5.13
• Node version: 22.14.0
• Operating System: macOS

Please show your full configuration:

import pluginVue from "eslint-plugin-vue";
import { defineConfigWithVueTs, vueTsConfigs } from "@vue/eslint-config-typescript";

export default defineConfigWithVueTs(
  {
    name: "app/files-to-lint",
    files: ["**/*.{ts,mts,tsx,vue}"],
  },

  {
    name: "app/files-to-ignore",
    ignores: ["**/dist/**", "**/dist-ssr/**", "**/coverage/**"],
  },

  pluginVue.configs["flat/recommended"],
  vueTsConfigs.recommended
);

What did you do?

const { msg } = defineProps<{
  msg?: string;
}>();

What did you expect to happen?
I switched from using the withDefaults to the new props destructure syntax and I expected the vue/require-default-prop to continue to check when defaults were not defined in the destructured object. I expected the above example to complain that I did not define defaults for msg.

What actually happened?
I got no errors in the above example.

Repository to reproduce this issue
https://github.com/hartbit/eslint-require-default-prop-destructured-issue

• The src/components/HelloWorld.vue component generates a warning, as expected, as it uses withDefaults,
• The src/components/HelloWordIssue.vue component does not generate a warning

[ZexTech]

The potentially unwanted change with this rule is that it now requires props to be defined (with undefined value).
This results in unnecessarily verbose code, despite the types being already correctly defined

// Before ✅
const { optional } = defineProps<{
  optional?: boolean;
  optionalLabel?: string;
}>();

// After ❌
const { optional, optionalLabel = undefined } = defineProps<{
  optional?: boolean;
  optionalLabel?: string;
}>();

Proposed solution could be to set this rule to off by default, minimizing the impact on users during the update to this version. This change would primarily affect users of the latest Vue 3.5 version who are utilizing destructured props.

Alternatively, a lint rule option could be introduced to require only that a default value is set, provided the property is explicitly added.
const { [key] } = defineProps<...

[yakobe]

I just got bitten by this. Now we have to destruct all the optional props even if they are only used in the template, just so we can assign as undefined.

Alternatively, a lint rule option could be introduced to require only that a default value is set, provided the property is explicitly added.

I think this might be a good compromise. Or maybe there would be a way to only require a default if for props that cannot be undefined. I'm not sure how that could be accomplished. Maybe something like this?:

const { optional } = defineProps<{
  optional?: boolean | undefined;
  optionalLabel?: string;
}>();