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.
I can't find it in the <script setup> docs at the moment, but I followed the script setup spec pretty closely, and I could have sworn that the name field of the component options is inferred from the name of the .vue file when script setup is used in Vue3. Can that functionality be added here? I've actually used patch-package to patch the transform to enable that functionality in my own dev environment, but I'd love to get it merged into the package proper, so that I don't have to maintain a patch file as I upgrade to different versions of this plugin.
I'd be happy to do the PR myself, if that would be helpful and if this was functionality you'd be ok with adding to the core plugin functionality.
The text was updated successfully, but these errors were encountered:
Also , I found that vue 3 also does not have SFC automatic name field generation. Maybe it's better for us to raise this question on https://github.com/vuejs/vue-next first.
You're right. I went through the script setup spec, and I couldn't find it anywhere. So I guess I'm just thinking of a conversation that happened in the RFC and it never made it to the official spec.
I can't find it in the
<script setup>
docs at the moment, but I followed thescript setup
spec pretty closely, and I could have sworn that thename
field of the component options is inferred from the name of the.vue
file whenscript setup
is used in Vue3. Can that functionality be added here? I've actually usedpatch-package
to patch the transform to enable that functionality in my own dev environment, but I'd love to get it merged into the package proper, so that I don't have to maintain a patch file as I upgrade to different versions of this plugin.I'd be happy to do the PR myself, if that would be helpful and if this was functionality you'd be ok with adding to the core plugin functionality.
The text was updated successfully, but these errors were encountered: