Replies: 3 comments 1 reply
-
I did find one way that should work for now, though I'd like to keep this discussion open to see if there's another way: const SomeThing = { /* component code here */ }
export default SomeThing Seems to do what I'm looking for. |
Beta Was this translation helpful? Give feedback.
-
This is expected behavior, see #82. But you can trigger auto import component in template, it will not end with |
Beta Was this translation helpful? Give feedback.
-
It would still be nice to be able to have an option to not add this suffix even when completing in the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Our project has several components like this:
When I start typing an import, the autosuggested import from Volar comes out like this:
Our standards however call for imports like this:
I don't mind having the
.vue
in the file path, that's not really going to affect our code. However, changing the import is a simple yet repetitive task that I think I should be able to configure either in Volar or through some kind of documentation hint in the component itself, but I can't find any documentation that supports this.Beta Was this translation helpful? Give feedback.
All reactions