Fixes#2767

If this approach doesn't align with the project's direction, please don't hesitate to reject this proposal. In that case, you may also close the corresponding issue.

What type of PR is this?

bug fix / enhancement

What does this PR do? / Why do we need it?

This PR fixes a regression in thevue/require-default-prop rule introduced in v10.1.0. The rule was requiring default values for ALL optional props when using props destructuring, even if those props were not included in the destructuring pattern.

Before this fix

// Was forced to destructure all optional props, even unused onesconst{ used, unused=undefined}=defineProps<{used?:string;unused?:string;// Only used in template, forced to assign undefined}>()

After this fix

// Only need to provide defaults for actually destructured optional propsconst{ used='default'}=defineProps<{used?:string;// Destructured, so needs defaultunused?:string;// Not destructured, no default needed}>()

What changes did you make? (Give an overview)

1. Modifiedlib/rules/require-default-prop.js:

   • Added logic to check if an optional prop is actually included in the destructuring pattern
   • Only requires default values for optional props that are explicitly destructured
   • Usesutils.getPropsDestructure(node) to get destructured props and check if optional prop exists

2. Updated test cases intests/lib/rules/require-default-prop.js:

   • Added valid test cases for optional props not included in destructuring
   • Updated invalid test cases to properly test mixed scenarios
   • Added comprehensive test coverage for the new behavior

Which issue(s) does this PR fix?

Fixes#2767
Related to#2725 and#2741

Additional context

This change maintains backward compatibility and only reduces false positive warnings. The rule continues to work as expected for:

• Required props (still checked)
• Optional props with explicit destructuring (still requires defaults)
• Boolean props (still exempt)
• Props usingwithDefaults() (still works)

The fix specifically addresses the user feedback that the previous fix was too aggressive and made Vue 3.5's props destructuring unnecessarily verbose.