You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The description of this in setup is inconsistent with the source code (#1063)
* The description of `this` in setup is inconsistent with the source code
* More accurate description of `this` in the setup function
Co-authored-by: skirtle <[email protected]>
* fix:Removed some formatted commas
Co-authored-by: coderwhy <[email protected]>
Co-authored-by: skirtle <[email protected]>
Copy file name to clipboardExpand all lines: src/guide/composition-api-introduction.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Now that we know the **why** we can get to the **how**. To start working with th
76
76
The new `setup` component option is executed **before** the component is created, once the `props` are resolved, and serves as the entry point for composition API's.
77
77
78
78
::: warning
79
-
Because the component instance is not yet created when `setup` is executed, there is no `this` inside a `setup`option. This means, with the exception of `props`, you won't be able to access any properties declared in the component – **local state**, **computed properties** or **methods**.
79
+
You should avoid using `this` inside `setup`as it won't refer to the component instance. `setup` is called before `data` properties, `computed`properties or `methods` are resolved, so they won't be available within `setup`.
80
80
:::
81
81
82
82
The `setup` option should be a function that accepts `props` and `context` which we will talk about [later](composition-api-setup.html#arguments). Additionally, everything that we return from `setup` will be exposed to the rest of our component (computed properties, methods, lifecycle hooks and so on) as well as to the component's template.
0 commit comments