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
{{ message }}
This repository was archived by the owner on Dec 25, 2024. It is now read-only.
This plugin seems to intentionally correct variable names in the ref object if they are covered by key names of other objects.
example:
<scriptsetup>
const listeners = computed(() =>({input: handleInput,}))constinput=ref(null);// renamed to input2</script>
However, the variable name modification is not done on the template side, so the ties are broken.
<scriptsetup>
const listeners = computed(() =>({input: handleInput,}))constinput=ref(null);// renamed to input2</script><template>
<!-- not renamed -->
<inputref="input"v-on="listeners""></template>
This does not seem to happen in Vue3 (variable names are not modified).
Expected behavior
As with Vue3, no intentional variable name modification is performed. However, I am not aware of how this feature was implemented so I am missing that consideration. Thanks.
Overview
This plugin seems to intentionally correct variable names in the ref object if they are covered by key names of other objects.
example:
However, the variable name modification is not done on the template side, so the ties are broken.
This does not seem to happen in Vue3 (variable names are not modified).
Expected behavior
As with Vue3, no intentional variable name modification is performed. However, I am not aware of how this feature was implemented so I am missing that consideration. Thanks.
Sample
Reproducible code can be found below.
https://github.com/ushironoko/unplugin-vue2-script-setup-not-renamed-template-ref
deps:
The text was updated successfully, but these errors were encountered: