Skip to content

content-assist proposals show up for annotation attribute names #1409

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
martinlippert opened this issue Nov 15, 2024 · 1 comment
Closed

content-assist proposals show up for annotation attribute names #1409

martinlippert opened this issue Nov 15, 2024 · 1 comment
Assignees
@martinlippert
Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: code completion type: bug
Milestone
4.27.0.RELEASE

Comments

@martinlippert
Copy link
Member 

@ConditionalOnProperty(<*>name = "my.prop")

results in content-assist proposals showing up with property keys and selecting a completion item results in name being replaced with the completion key, which is completely wrong. There should be no completion showing up from our side instead.
@martinlippert martinlippert added type: bug for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: code completion labels Nov 15, 2024
@martinlippert martinlippert added this to the 4.27.0.RELEASE milestone Nov 15, 2024
@martinlippert martinlippert self-assigned this Nov 15, 2024
martinlippert added a commit that referenced this issue Nov 15, 2024
@martinlippert
GH-1409: do not compute completion proposals when cursor is on attrib…
0b90be1 
…ute name instead of value
@martinlippert
Copy link
Member Author

Fixed with 0b90be1

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@martinlippert martinlippert

Labels
for: eclipse something that is specific for Eclipse for: vscode something that is specific for VSCode theme: code completion type: bug
Projects
None yet
Milestone
4.27.0.RELEASE
Development

No branches or pull requests
1 participant
@martinlippert