forked from eclipse-jdt/eclipse.jdt.core
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fixes testBug519493_003 - module binding on class symbol #612
Open
robstryker
wants to merge
866
commits into
eclipse-jdtls:dom-with-javac
Choose a base branch
from
robstryker:testBug519493_003
base: dom-with-javac
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fixes testBug519493_003 - module binding on class symbol #612
robstryker
wants to merge
866
commits into
eclipse-jdtls:dom-with-javac
from
robstryker:testBug519493_003
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This seems to introduce some new failures:
Let's first rebase to check whether those vanish. |
7fa6490
to
d4193c8
Compare
2dd9a99
to
193c59d
Compare
When I run these tests locally, I'm not seeing much of a difference at all between with the PR or without the PR. This is very strange. |
c02519d
to
e65aeb8
Compare
612291f
to
d1f814c
Compare
193c59d
to
72837e7
Compare
Rebased, Will investigate what it does to tests. |
2b02636
to
a40c063
Compare
13a7ce9
to
911e4b3
Compare
16bd705
to
9fb5696
Compare
7b4b9ad
to
e230daa
Compare
0575d89
to
6dd73f3
Compare
df710af
to
fbcc030
Compare
2ad1e11
to
f45e071
Compare
7f5c20a
to
87832d6
Compare
aa3b08f
to
cc0dccd
Compare
7e220b3
to
525cd23
Compare
630ab89
to
141942c
Compare
b7877ed
to
96f35d1
Compare
eg. preserve the `m[]` in the AST in the following case, (despite the fact that it's invalid), since javac does. ```java int[] foo = new int[m[]]; ``` Signed-off-by: David Thompson <[email protected]>
This causes 6 regerssions because 'possible this escape' is now reported. Signed-off-by: David Thompson <[email protected]>
- fix a bug related to ordering of tag names - get `@param| ` completion to work as expected - use `DOMCompletionUtil.findParent` instead of only checking the direct parent when calculating the node to use as context for completion (in the case of nodes within `Javadoc`) - split out `MemberRef` and `MethodRef` to their own completion cases - for now these are stubs - move the logic for type completion for `@see` and `@link` under the TagElement section, as it should be handled differently than the "default completion": - improve handling of qualified references - for the time being, suggest nothing when completing a type from a specific module. i.e. `@see java.base/java.util.|` no longer gives any results. Signed-off-by: David Thompson <[email protected]>
Also needed but missed.
Note that there are two code paths: one through `MemberRef` and another through an `@link` or `@see` `TagElement`. This is because the AST conversion tests expect the following to be a `TextElement` instead of a `MemberRef`: ```java /** * @see MyClass# */ ``` (and also:) ```java /** * @see # */ ``` However, the completion tests expect completion for MyClass' members to work in this case. Fixes eclipse-jdt#1103 Signed-off-by: David Thompson <[email protected]>
* Type parameters * Annotations * Relevance
* Support type restriction for SwitchCase * Support for QualifiedType * Fix CompletionContext.getExpectedTypesSignatures()
* Return more proposals * Do no repeat extra import in proposals
- Fixes for the relevance numbers for methods in javadoc - Suggest constructors (including the default constructor) in `@see` and `@link` - Do not show completion when completing parameter name in method reference in Javadoc - when referencing a method from Javadoc, and the cursor is in the method parameters, specifically right after a `(` or `,`, complete the entire method signature This should fix 37 test cases Signed-off-by: David Thompson <[email protected]>
96f35d1
to
1901a3c
Compare
Signed-off-by: Rob Stryker <[email protected]>
72837e7
to
a3d54e0
Compare
9c17bb6
to
4516c31
Compare
a1bf22f
to
0b6fd1c
Compare
7ad387c
to
c52dfb2
Compare
c52dfb2
to
76e9c9c
Compare
838c386
to
40594bf
Compare
15d0bf3
to
811bae7
Compare
c906abc
to
b53a413
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.