VTL for Vue 3: expose the RenderOptions type
See original GitHub issueI would like the RenderOptios type to be exposed so i can create a typed DeepPartial<RenderOptios>
prop on my factory function. Example: https://lmiller1990.github.io/vue-testing-handbook/components-with-props.html#refactor-with-a-factory-function
index.d.ts, line 45:
export type RenderOptions = VueTestingLibraryRenderOptions &
VueTestUtilsRenderOptions
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
How to Use Vue 3 Expose in Composition and Options API
This tutorial will cover on using vue 3 expose in composition and options api. Vue 3 offers many tools to create web applications....
Read more >Understanding Vue 3's "expose" - Vue Mastery
I have purposely chosen to do the first example using the composition API because of the second use case of the expose function,...
Read more >Render Functions & JSX | Vue.js
Declaring Render Functions The render function is declared inside setup() so it naturally has access to the props and any reactive state declared...
Read more >Typescript error on render with a defineComponent (v6.0) #167
This error is reported by typescript : Argument of type 'DefineComponent<{}, ... RenderOptions } from '@testing-library/vue' import Vue, ...
Read more >how to expose component methods in render function in vue3 ...
Component instance can be extended by using expose , this is useful for cases where setup return value is already render function: type...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi! you might need to fork the repo and submit a PR from repository to repository, instead of branch to branch
🎉 This issue has been resolved in version 6.4.2 🎉
The release is available on:
Your semantic-release bot 📦🚀