fix(compiler-sfc): support using other prop as default value in props destructuring

[edison1105]

close #12386

[github-actions]

Size Report

Bundles

File	Size	Gzip	Brotli
runtime-dom.global.prod.js	100 kB	38 kB	34.2 kB
vue.global.prod.js	159 kB	57.9 kB	51.4 kB

Usages

Name	Size	Gzip	Brotli
createApp (CAPI only)	46.9 kB	18.3 kB	16.7 kB
createApp	55 kB	21.3 kB	19.4 kB
createSSRApp	59 kB	23 kB	21 kB
defineCustomElement	59.8 kB	22.8 kB	20.8 kB
overall	68.7 kB	26.3 kB	24 kB

[pkg-pr-new]

Open in Stackblitz

@vue/compiler-core

pnpm add https://pkg.pr.new/@vue/compiler-core@12387

@vue/compiler-ssr

pnpm add https://pkg.pr.new/@vue/compiler-ssr@12387

@vue/compiler-dom

pnpm add https://pkg.pr.new/@vue/compiler-dom@12387

@vue/compiler-sfc

pnpm add https://pkg.pr.new/@vue/compiler-sfc@12387

@vue/reactivity

pnpm add https://pkg.pr.new/@vue/reactivity@12387

@vue/runtime-core

pnpm add https://pkg.pr.new/@vue/runtime-core@12387

@vue/runtime-dom

pnpm add https://pkg.pr.new/@vue/runtime-dom@12387

@vue/server-renderer

pnpm add https://pkg.pr.new/@vue/server-renderer@12387

@vue/shared

pnpm add https://pkg.pr.new/@vue/shared@12387

vue

pnpm add https://pkg.pr.new/vue@12387

@vue/compat

pnpm add https://pkg.pr.new/@vue/compat@12387

commit: 038dc1e

[vue-bot]

⏳ Triggered ecosystem CI: Open

[vue-bot]

📝 Ran ecosystem CI: Open

suite	result	latest scheduled
language-tools	✅ success	✅ success
nuxt	✅ success	✅ success
pinia	✅ success	✅ success
primevue	✅ success	✅ success
quasar	✅ success	✅ success
radix-vue	✅ success	✅ success
router	✅ success	✅ success
test-utils	✅ success	✅ success
vant	✅ success	✅ success
vite-plugin-vue	✅ success	✅ success
vitepress	✅ success	✅ success
vue-i18n	✅ success	✅ success
vue-macros	✅ success	✅ success
vuetify	✅ success	✅ success
vueuse	✅ success	✅ success
vue-simple-compiler	✅ success	✅ success

[skirtles-code]

Do you think a use case like this should be supported?

const { items, start = 0, end = items.length } = defineProps<{
  items: string[],
  start?: number,
  end?: number
}>()

• Playground

I'm also wondering about the impact of prop ordering. For example, this will work:

const { a = 0, b = a } = defineProps<{
  a?: number,
  b?: number,
}>()

But this (with a and b flipped in the type) won't:

const { a = 0, b = a } = defineProps<{
  b?: number,
  a?: number,
}>()

• Playground

In some ways this isn't a new problem, as the ordering has always mattered, but it's maybe less intuitive when the defaults are being applied via props destructuring.