Update invoking-child-methods.md #42
Conversation
| - If you're using an explicit `setup` function, you'll need to return the method from `setup`, even if it isn't used in the child's own template. Anything returned from `setup` will be accessible via the template ref, unless you explicitly opt out by using the [`expose`](https://vuejs.org/api/options-state.html#expose) option. | ||
| - If the child is using the Options API, any method in the child's `methods` section will be accessible via the template ref, unless you're using the [`expose`](https://vuejs.org/api/options-state.html#expose) option to opt out. | ||
|
|
||
| ## Debugging problems |
There was a problem hiding this comment.
This looks for me as a good candidate for its own page
There was a problem hiding this comment.
Agreed, it should really be moved to template-ref.md, which covers Why are my template refs not working?. I'll leave it here for now and move it when I finish off that page.
There was a problem hiding this comment.
I actually meant a more general page about debugging or at least debugging refs, not just template refs. It's a common problem that people are doing console.log(some ref/reactive/plain object) and wondering why it shows the data but ref.value.foo throws an error or shows different data.
There was a problem hiding this comment.
Ah, OK, that'd be closer to logging-is-live.md, or at least it will be when I get round to writing it properly. It's not entirely clear to me yet how many pages we need for that topic.
|
Based on the feedback I received, I've added two new sections to the end, Using props instead and Using |
This PR updates the answer to the question How do I call a method of a child component?.
The previous answer was a stub and has been completely replaced, though the core ideas remain the same.