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.

Sign up for GitHub

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

Jump to bottom

Organize Imports action doesn't show an import dialog if more than one import is possible for unresolved reference #8593

Closed
vinokurig opened this issue Feb 2, 2018 · 1 comment
Closed

Organize Imports action doesn't show an import dialog if more than one import is possible for unresolved reference #8593

vinokurig opened this issue Feb 2, 2018 · 1 comment
Assignees
@tolusha
Labels
kind/bug Outline of a bug - must adhere to the bug report template. target/branch Indicates that a PR will be merged into a branch other than master.

Comments

@vinokurig
Copy link
Contributor

Description

Organize Imports action doesn't show an import dialog if more than one import is possible for unresolved reference

Reproduction Steps

  1. Create a simple java project.
  2. Open a Java class and introduce a List variable, List should be underlined by wavy red line. It means that List is not resolved.
  3. Go to menu Assistant -> Organize Imports
    WRONG: Nothing happenes.
    Expected: Organize Imports dialog must appear to propose an import.

OS and version:
JDT LS branch

Diagnostics:
@vinokurig vinokurig added kind/bug Outline of a bug - must adhere to the bug report template. target/branch Indicates that a PR will be merged into a branch other than master. team/languages labels Feb 2, 2018
@tsmaeder tsmaeder mentioned this issue Feb 2, 2018
Closed
8 tasks
@tolusha
Copy link
Contributor

tolusha commented Feb 9, 2018

organizeimports

@tsmaeder tsmaeder mentioned this issue Feb 12, 2018
Closed
15 tasks
@tolusha tolusha added the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 12, 2018
This was referenced Feb 14, 2018
Merged
Merged
@tolusha tolusha self-assigned this Feb 20, 2018
@tolusha tolusha removed the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 20, 2018
@tolusha tolusha closed this as completed Feb 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tolusha tolusha

Labels
kind/bug Outline of a bug - must adhere to the bug report template. target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tolusha @vinokurig