Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: remove list styles #3209

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: remove list styles #3209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions src/guide/extras/web-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,8 +307,7 @@ declare module 'vue' {
Here is the recommended way to enable type checking in SFC templates of Custom Elements that are not built with Vue.

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

Suppose we have a custom element with some JS properties and events defined, and it is shipped in a library called `some-lib`:
Expand Down Expand Up @@ -391,10 +390,7 @@ type VueEmit<T extends EventMap> = EmitFn<{
```

:::tip Note
- 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.
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.
:::

Using the type helper we can now select the JS properties that should be exposed for type checking in Vue templates:
Expand Down