Skip to content

Commit 289894a

Browse files
committed
docs: remove list styles
1 parent b70003e commit 289894a

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

src/guide/extras/web-components.md

+2-6
Original file line numberDiff line numberDiff line change
@@ -307,8 +307,7 @@ declare module 'vue' {
307307
Here is the recommended way to enable type checking in SFC templates of Custom Elements that are not built with Vue.
308308

309309
:::tip Note
310-
- This approach is one possible way to do it, but it may vary depending on the
311-
- framework being used to create the custom elements.
310+
This approach is one possible way to do it, but it may vary depending on the framework being used to create the custom elements.
312311
:::
313312

314313
Suppose we have a custom element with some JS properties and events defined, and it is shipped in a library called `some-lib`:
@@ -391,10 +390,7 @@ type VueEmit<T extends EventMap> = EmitFn<{
391390
```
392391
393392
:::tip Note
394-
- We marked `$props` and `$emit` as deprecated so that when we get a `ref` to
395-
- a custom element we will not be tempted to use these properties, as these
396-
- properties are for type checking purposes only when it comes to custom elements.
397-
- These properties do not actually exist on the custom element instances.
393+
We marked `$props` and `$emit` as deprecated so that when we get a `ref` to a custom element we will not be tempted to use these properties, as these properties are for type checking purposes only when it comes to custom elements. These properties do not actually exist on the custom element instances.
398394
:::
399395
400396
Using the type helper we can now select the JS properties that should be exposed for type checking in Vue templates:

0 commit comments

Comments
 (0)