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

Running Fix Imports leaves files unsaved #32

Open
emme1444 opened this issue Dec 14, 2020 · 2 comments
Open

Running Fix Imports leaves files unsaved #32

emme1444 opened this issue Dec 14, 2020 · 2 comments

Comments

@emme1444
Copy link

emme1444 commented Dec 14, 2020

When invoking the Fix Imports command files are processed, but then left unsaved (still showing a dot). Only to have to save them again. I'm mostly using this with the fixOnSave option enabled. That's why it's bothering me. Meaning I have to save all files twice every time. Not too bothersom, but it adds up and is not that clean in my opinion. Here's an example:

I don't know if this is because it's running the Organize Imports action. Couldn't tell since I haven't looked into the code, but might be something to do with that. I don't know, but feels like the vscode api would expose some method of saving the file. Maybe that's sufficient?

Anyway, hope we can fix this!
Let me know if there's anything else.

@luanpotter
Copy link
Member

Agreed it should save, if anyway wants to help with a fix that would be great! :)

@allanwolski
Copy link

It would be great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants