Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Literal String Union Autocomplete now working inside .vue file
See original GitHub issueInfo
- Platform: Win10 Home
- Vetur version: 0.27.3
- VS Code version: 1.49.1
Problem
Autocomplete for string literal union type not working inside .vue file (with <script lang="ts"> ). But working just fine inside .ts file.
Working nice in test.ts
No autocomplete, only information in test.vue
Reproducible Case
Declare any kind of type with string literal union type. Expected: Give autocomplete just as in a .ts file. Reality: No autocomplete in .vue file
Note: I’m not really sure where to post this: vue, vetur or vscode. And i also not really sure whether this should be a bug report or feature request. But since in the vetur doc they said that
The IntelliSense should be almost the same to the IntelliSense in js/ts files So maybe this is the right place to post this.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
https://github.com/vuejs/vetur/commit/aaff6be212d24ef25ba0156b825504fb1c250521
I cannot recall why I made this change. I’ll revert it for now. If I do encounter the bug I’ll fix it again…
@octref any news on this ? In the meantime i think i would rather has that unwanted completion than not auto-complete at all. Literal String Union is a great way to restraint option, I use them alot and auto-complete will help alot in vue file. Unwanted completion can be cancel with a simple
Esc. The benefit outweight the uncomfortable IMO