-
Notifications
You must be signed in to change notification settings - Fork 16
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
Does not trigger re-render on props change #12
Comments
yuichkun
changed the title
Does not work with values that changes afterwards
Does not trigger re-render on props change
Mar 23, 2021
You're always welcome to create a PR :)
Am Di., 23. März 2021 um 09:42 Uhr schrieb Yuichi Yogo <
***@***.***>:
… TL;DR
Hi, thank you very much for this awesome library!
Although this works with many cases, I found a situation where v-linkified
component does not re-render after changes via props, data, computed, etc.
Reproduction
Demo:
https://vue-linkify-not-working-demo.vercel.app/
Source Code:
https://github.com/yuichkun/repro-vue-linkify-bug
Possible Fix?
I guess this bug derives from the fact that this library gets text values
from el.innerHTML, so if there's a way to get text from vNode, it could
avoid referencing the old value??
I'm not too familiar with Vue.js but if @phanan
<https://github.com/phanan> is busy, I'm up for trying making up a fix PR
myself :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5O3UQOQG2UAJIXX4BIMR3TFBIAHANCNFSM4ZUW3PJA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
Hi, thank you very much for this awesome library!
Although this works with many cases, I found a situation where
v-linkified
component does not re-render after changes via props, data, computed, etc.Reproduction
Demo:
https://vue-linkify-not-working-demo.vercel.app/
Source Code:
https://github.com/yuichkun/repro-vue-linkify-bug
Possible Fix?
I guess this bug derives from the fact that this library gets text values from
el.innerHTML
, so if there's a way to get text fromvNode
, it could avoid referencing the old value??I'm not too familiar with Vue.js but if @phanan is busy, I'm up for trying making up a fix PR myself :)
The text was updated successfully, but these errors were encountered: