-
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
Incorrect signatures returned assertEquals #1290
Comments
@NikolasKomonen AFAICS you are showing the information from |
@NikolasKomonen in vscode, you need to enable signatureHelp with |
Thanks, I just tested it. For sure not doing what it is supposed to. I'll look into it. |
@fbricon one more thing: I noticed that ParameterInformation.documentation field is not populated. Is this intentional? |
@yyoncho I don't think so. Please open a separate ticket for that problem |
I found the problem area, but I think @snjeza would be more knowledgeable since she worked on it. package com.example.demo;
import static org.junit.Assert.assertEquals;
import org.junit.Test;
public class DemoApplicationTests {
@Test
public void contextLoads() {
long num = 3;
assertEquals(num,num);
}
} If I do Ctrl+Shift+Space here: assertEquals(|num,num); the variable but when I do it here: assertEquals(n|um,num); It triggers this case and populates the I just wanted to see if you knew what to fix before I dove deeper into the issue. |
signature help shows
(Object[], Object[])
as the active signature instead of (long, long).The text was updated successfully, but these errors were encountered: