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

No completion suggestions for qualified statements when matchCase is set to firstLetter #2925

Closed
hopehadfield opened this issue Oct 24, 2023 · 1 comment · Fixed by #2989
Closed

Comments

@hopehadfield
Copy link
Contributor

See below.

Peek 2023-10-24 11-40

This is because the matchCase function relies on the context to determine the first letter match. In this case, the context identifies the token as the text after the "." (util). The proposal, however, holds the fully qualified name (java.util.*), thus the first letters don't match.

cc @testforstephen @jdneo

@rgrunber
Copy link
Contributor

rgrunber commented Oct 24, 2023

As a workaround (in the event fixing the context is too complicated), I wonder if we could just opt package references out of respecting matchCase. They aren't computationally intensive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants