-
Notifications
You must be signed in to change notification settings - Fork 47
fix: 使用nextTick解决vue2下ref不存在的问题 #75
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.
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vue-demi
在 vue2 环境下引用了 @vue/composition-api
包,里面有提到 $refs undefined 的问题,可以用 vue2 专属的 setupContext.refs
来获取。
不过我认为 vue-demi
要完全兼容 vue2 还是挺麻烦的,比如我在 #73 提到的两个问题
v-model
没法正常使用,需要判断如果是 vue2 则用value
,input
来代替modelValue
,update:modelValue
$listeners
没法在 vue3 里面用,在开发@wsfe/vue-tree
的时候一般是 vue3 环境,会报类型错误
Won't fix as mentioned in #87
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
fix #73