Add support for props destructure

[ota-meshi]

Tell us about your environment

• ESLint version: v8.36.0
• eslint-plugin-vue version: v9.10.0
• Node version: v18.12.1

The problem you want to solve.

Add support for props destructure. It will be introduced in Vue 3.3.

<script setup lang="ts">
const { foo = 1, bar = 'ok' } = defineProps<{ foo?: number, bar?: string }>()
</script>

Your take on the correct solution to problem.

I think we should at least change the rules in the following list.

• Change vue/no-setup-props-reactivity-loss rule.
  Destructuring assignment immediately after defineProps() is allowed.
  Add support for props destructure to vue/no-setup-props-reactivity-loss rule #2550
  However, Vue2 doesn't allow to use props destructure, so we may need to split rules.
• Change vue/require-valid-default-prop rule.
  Add support for props destructure to vue/require-valid-default-prop rule #2551
• Change vue/require-default-prop rule.
  Add support for props destructure to vue/require-default-prop rule #2552
• Change vue/no-boolean-default rule.
  We need to support a new way to specify defaults.
  Add support for props destructure to vue/no-boolean-default rule #2553
• Change vue/no-required-prop-with-default rule.
  Add support for props destructure to vue/no-required-prop-with-default rule #2560
• Change suggestion of vue/no-restricted-props rule.
  Add support for props destructure to vue/no-restricted-props rule #2562

Additional context

vuejs/core#7986

[ota-meshi]

Since it's still an experimental feature, eslint-plugin-vue won't support it yet until it's GA.

https://blog.vuejs.org/posts/vue-3-3#experimental-features

[n0099]

It's stable now: https://blog.vuejs.org/posts/vue-3-5#reactive-props-destructure

[henribru]

Perhaps a bit niche, but an optional rule that bans props destructure could also be useful, to keep consistency with existing code that doesn't use it.

Or perhaps one that you can configure to either enforce that everything uses props destructure or that nothing does.

[ota-meshi]

I believe we have merged the necessary changes into the master branch so I will close this issue.