Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Error performing autoimport: Unknown autocomplete suggestion type mixin #114

Open
samu opened this issue Sep 13, 2019 · 6 comments
Open

Comments

@samu
Copy link

samu commented Sep 13, 2019

When i try to use the "add import for" feature, i get the following error:

Error performing autoimport: Unknown autocomplete suggestion type mixin
@samu
Copy link
Author

samu commented Sep 18, 2019

It looks like this is due to the absence of a .classpath file in my project folder.

I tried to open the same project with vs code and the java extension - then, .classpath was generated automatically. Now, the "add import for" feature works in atom.

I wonder what exactly the vs code extension is doing differently. Any advice?

@MarceloLaser
Copy link

Am having the same issue. Just thought I'd add my voice since this has been open for three months without comment.

@mdiin
Copy link
Contributor

mdiin commented Feb 18, 2020

I ran into this today trying to auto-import a Spring annotation. It turns out atom-languageclient considers annotations to be of type mixin, which is a case not handled by autoImportActionProvider.js#buildImportSuggestion. I will open a PR containing a fix shortly.

@m-lnrs
Copy link
Contributor

m-lnrs commented Apr 30, 2020

Hello @mdiin,
I've seen your fix (#120) for this issue. I was with a similar problem that seems to me is possible to solve the same way.

Trying to use the "add import for..." feature on an enum, the following error rises:

error performing autoimport: unknown autocomplete suggestion type enum

Adding case 'enum': the same way you did with case 'mixin': seems to solve the problem as well. If that is the proper way to solve this problem, can you include this one more line to your fix or is it better to create another issue/pull request for this?

Thanks.

@mdiin
Copy link
Contributor

mdiin commented May 19, 2020

Hi @m-lib,

I think you should create another PR for that fix, since it is orthogonal to the fix in #120.

Sorry for the late reply.

@m-lnrs
Copy link
Contributor

m-lnrs commented Sep 4, 2020

Thank you very much @mdiin :-D

I've been using your solution in a while for now. It's working like a charm!

Thanks.

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

No branches or pull requests

4 participants