-
Notifications
You must be signed in to change notification settings - Fork 408
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
Sort the quick fix menu for imports in a order that makes sense #550
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than expecting a different, seemingly random, order like assertCodeActions(cu, e3, e1, e2, e4); in those tests assertions, I'd rather keep the assertions intact and rearrange the Expected instance declarations instead.
I understand it's more tedious to do now, but it will be more maintainable on the long term
@@ -133,4 +136,19 @@ private static CompilationUnit getASTRoot(ICompilationUnit unit) { | |||
return SharedASTProvider.getInstance().getAST(unit, new NullProgressMonitor()); | |||
} | |||
|
|||
class CUCorrectionProposalComparator implements Comparator<CUCorrectionProposal> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
private static class
I'm definitely getting a different sort. And I rebuilt the server 3 times. I need to figure out why. FWIW, I'm using the latest vscode insiders build (1.21.0-insider 00f2d8ed7196606d31cc1759a171486d1cc00deb) |
The issue can be reproduced when using VS Code >= 1.20 |
Signed-off-by: Snjezana Peco <snjezana.peco@redhat.com>
@fbricon I have updated the PR. |
Fixes redhat-developer/vscode-java#424
Signed-off-by: Snjezana Peco snjezana.peco@redhat.com