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

Add support for CompletionList "applyKind" to control how defaults and per-item commitCharacters/data are combined #1558

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

DanTup
Copy link
Contributor

@DanTup DanTup commented Sep 18, 2024

Implements the changes in the LSP spec PR at microsoft/language-server-protocol#2018 (see also microsoft/language-server-protocol#1802).

Please let me know if you think there are any additional test cases that need covering.

@DanTup
Copy link
Contributor Author

DanTup commented Sep 26, 2024

@dbaeumer FYI in case you didn't see this :)

Looks like one of the status checks is stuck too (not the approval one, but vscode-languageserver-node).

@dbaeumer
Copy link
Member

I was out the last 1 1/2 weeks. Will have a look this week.

Copy link
Member

@dbaeumer dbaeumer left a comment

Choose a reason for hiding this comment

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

The rest looks good to me.

*
* @since 3.18.0
*/
export namespace ApplyKind {
Copy link
Member

Choose a reason for hiding this comment

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

I missed that on the spec side. Usually we only use string enums for enum kinds that are extensible from the server side and then type them as strings. To make things consistent I would say we should use numbers instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure - I've pushed f8ed433 + 5e28745 with this change and some minor tweaks, and equiv changes in microsoft/language-server-protocol#2018

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

Successfully merging this pull request may close these issues.

2 participants