-
Notifications
You must be signed in to change notification settings - Fork 108
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
fix(Scope): set closestMatch when member type not found #466
base: master
Are you sure you want to change the base?
Conversation
with eclipse-platform/eclipse.platform.releng.aggregator I managed to compile it. but cannot execute the test cases. |
6746d26
to
ad6084d
Compare
Bellow CI error seems environment issue: https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Github/job/PR-466/3/console |
If you are still interested on a fix, could you please rebase your PR on master state? Note, the compiler code moved to a dedicated project. |
@fishautumn : two issues:
|
21a83d0
to
c9e39a7
Compare
thanks @iloveeclipse for pointing out the issues. I've update the commits for correct email. about the test case, I think it makes sense to give completions for given code. so I simply updated it. |
fixed string constant in test. |
I see some tests modified but I don't understand the problem we are trying to fix here. |
LambdaExpressionsTest.test045: changed code causing 1 more error message reported. It can be avoided if necessary. I will try to add a case for the issue in future. |
What it does
fix #465. set closestMatch when member type not found
How to test
I cannot manage to compile the project. As it's pretty simple, just waiting for automatic workflows.
Author checklist