Skip to content

New Completion Trigger Kind#308

Merged
aeschli merged 4 commits intomasterfrom
dbaeumer/TriggerForIncompleteCompletions
Feb 13, 2018
Merged

New Completion Trigger Kind#308
aeschli merged 4 commits intomasterfrom
dbaeumer/TriggerForIncompleteCompletions

Conversation

@ramya-rao-a
Copy link
Contributor

No description provided.

@ramya-rao-a ramya-rao-a requested a review from dbaeumer February 11, 2018 04:06
@rcjsuen
Copy link
Contributor

rcjsuen commented Feb 11, 2018

If a new constant is going to be added, please update the specification also.

@ramya-rao-a
Copy link
Contributor Author

@rcjsuen I believe the specification maps to the current release where as the changes in this PR map to the pre-release version.

@dbaeumer Is there any version of the specification where we should update the pre-release changes?

@aeschli aeschli merged commit b8f7cb9 into master Feb 13, 2018
@aeschli
Copy link
Contributor

aeschli commented Feb 13, 2018

The changes look good to me. The contextSupport is new for 4.0, so no need to add an additional client capability.

@rcjsuen
Copy link
Contributor

rcjsuen commented Feb 13, 2018

@ramya-rao-a The current specification of the LSP is v3 but it is still receiving updates on a regular basis. In fact, CompletionTriggerKind did not originally exist in v3 but was only recently added in November.

In any case, I have opened microsoft/language-server-protocol#403 to update the protocol to include the new TriggerForIncompleteCompletions you added.

@dbaeumer
Copy link
Member

@ramya-rao-a in general the spec needs to be updated as well when we do something in code :-).

@rcjsuen thanks for updating the spec

@ramya-rao-a
Copy link
Contributor Author

@rcjsuen @dbaeumer Thanks, I'll keep that in mind for the next time.

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.

4 participants