Imports to Components were inserted to random positions.
See original GitHub issue- I have searched through existing issues
- I have read through docs
- I have read FAQ
- I have tried restarting VS Code or running
Vetur: Restart VLS
Info
- Platform: Windows
- Vetur version: 0.30.3
- VS Code version: 1.51.1
Problem
When editing the template of a component with help from IntelliSense auto completion and typing the component name as a tag name, even if already declared, a new import is still generated, its contents being inserted to random positions in the script
part of the Vue code.
Reproducible Case
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Python import: Advanced Techniques and Tips
In Python, you use the import keyword to make code in one module available in another. Imports in Python are important for structuring...
Read more >Building a 10x10 array with elements placed in random ...
Hello, I'd like to build a numerosity discrimination task. In each trial, subjects are presented with an imaginary 10x10 array with 31 to...
Read more >Imports - checkstyle
Rationale: Importing all classes from a package or static members from a class leads to tight coupling between packages or classes and might ......
Read more >Importing assets - Unity - Manual
Unity automatically detects files as they are added to the Assets folder, or if they are modified. When you put any asset into...
Read more >Create Random Points (Data Management)—ArcGIS Pro
Points will be randomly placed inside polygon features, along line features, or at point feature locations. Each feature in this feature class will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This happens for me as well. The project I’m writing in doesn’t use typescript either.
A few strange things happen:
import
statement and the component definition don’t respect the correct indentation (in this project everything inside<script>
tags is indented 2 spaces minimum).Any update on this? This bug is absolutely detrimental to developer experience and is still here in 0.35.0.
Sidenote, to me the “no repro case” label seems kind of dubious as this bug happens to me in literally every Vue 2 project where Vetur is active.