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.

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

8285150: Improve tab completion for annotations #22840

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lahodaj
Copy link
Contributor

@lahodaj lahodaj commented Dec 20, 2024

When using types code like:

@Deprecated(

and presses <tab>, there should be a sensible completion, but currently there is nothing. This PR proposes to add code completion for annotation attributes.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8285150: Improve tab completion for annotations (Enhancement - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22840/head:pull/22840
$ git checkout pull/22840

Update a local copy of the PR:
$ git checkout pull/22840
$ git pull https://git.openjdk.org/jdk.git pull/22840/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22840

View PR using the GUI difftool:
$ git pr show -t 22840

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22840.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 20, 2024

👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Dec 20, 2024

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 20, 2024
@openjdk
Copy link

openjdk bot commented Dec 20, 2024

@lahodaj The following label will be automatically applied to this pull request:

  • kulla

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@mlbridge
Copy link

mlbridge bot commented Dec 20, 2024

Webrevs

}
if (tp.getParentPath().getLeaf().getKind() == Kind.NEW_ARRAY &&
((NewArrayTree) tp.getParentPath().getLeaf()).getInitializers().contains(tp.getLeaf())) {
return isAnnotationAttributeValue(tp.getParentPath());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recall JLS requires annotation arrays to be one-dimensional only, but this check seems to allow multi-dimensional arrays with annotation elements.

@@ -949,6 +1024,17 @@ private Predicate<Element> createAccessibilityFilter(AnalyzeTask at, TreePath tp
};
}

private boolean isAnnotationAttributeValueType(AnalyzeTask at, TypeMirror type) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This name is misleading - it is checking if a static final field type is suitable for an annotation attribute. This is more restrictive than general annotation element return types, which also allows annotation interfaces and one-dimensional arrays of primitives, enums, strings, and annotation interfaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kulla [email protected] rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

2 participants