From 231aeb4685c6182af17ee51c2b307a13b1def89f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ismae=CC=88l=20Maurice?= Date: Sat, 23 Nov 2024 08:25:56 +0100 Subject: [PATCH] Fix(web-component): Set right link #3110 #3110 --- src/guide/extras/web-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/extras/web-components.md b/src/guide/extras/web-components.md index 75b72bbc17..a383bebb33 100644 --- a/src/guide/extras/web-components.md +++ b/src/guide/extras/web-components.md @@ -274,7 +274,7 @@ export function MyComponent() { When writing Vue SFC templates, you may want to [type check](/guide/scaling-up/tooling.html#typescript) your Vue components, including those that are defined as custom elements. -Custom elements are registered globally in browsers using their built-in APIs, and by default they won't have type inference when used in Vue templates. To provide type support for Vue components registered as custom elements, we can register global component typings by augmenting the [`GlobalComponents` interface](https://github.com/vuejs/language-tools/blob/master/packages/vscode-vue/README.md#usage) for type checking in Vue templates (JSX users can augment the [JSX.IntrinsicElements](https://www.typescriptlang.org/docs/handbook/jsx.html#intrinsic-elements) type instead, which is not shown here). +Custom elements are registered globally in browsers using their built-in APIs, and by default they won't have type inference when used in Vue templates. To provide type support for Vue components registered as custom elements, we can register global component typings by augmenting the [`GlobalComponents` interface](https://github.com/vuejs/language-tools/wiki/Global-Component-Types) for type checking in Vue templates (JSX users can augment the [JSX.IntrinsicElements](https://www.typescriptlang.org/docs/handbook/jsx.html#intrinsic-elements) type instead, which is not shown here). Here is how to define the type for a custom element made with Vue: