Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capability to specify auto-import style #1297

Closed
cmeyertons opened this issue May 18, 2019 · 7 comments
Closed

Capability to specify auto-import style #1297

cmeyertons opened this issue May 18, 2019 · 7 comments

Comments

@cmeyertons
Copy link

  • [X ] I have searched through existing issues
  • [X ] I have read through docs
  • [ X] I have read FAQ

Info

  • Platform:
  • Vetur version: 0.21.0
  • VS Code version: 1.33.1

Problem

VS Code Typescript has to capability to specify auto-import module behavior to prefer non-relative imports -- would be great if Vetur either respected the Typescript setting or had the same capability

image

Reproducible Case

  1. Set typescript -> preferences -> import module specifier to non-relative
  2. perform an auto-import
  3. Vetur uses a relative import
@jsmitar
Copy link

jsmitar commented Jun 20, 2019

I have the same problem

@cainaf
Copy link

cainaf commented Sep 27, 2019

this would be really nice

@octref octref changed the title Capability to specify auto-import Capability to specify auto-import style Nov 11, 2019
@TimeBandit
Copy link

TimeBandit commented Nov 28, 2019

I need this, my life depends on it 🤯

@WORMSS
Copy link

WORMSS commented Dec 12, 2019

I've had to do a lot of additional imports in quite a few classes today and it always importing a massive bunch of ../../../../.. is really starting to grate

@bobmoff
Copy link

bobmoff commented Feb 17, 2020

Yep. Its annoying. A workaround is to instead of using the autocomplete, click the yellow lightbulb. That way the import added is non-relative.

@Janther
Copy link

Janther commented Apr 6, 2020

I'd like this as well :)

@octref
Copy link
Member

octref commented Aug 3, 2020

Duplicate of #1177, which is fixed by #1753.

@octref octref closed this as completed Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants