Skip to content

DidOpenTextDocumentParams does not extend TextDocumentIdentifier#36

Merged
dbaeumer merged 1 commit intomicrosoft:masterfrom
Marwes:patch-1
Jul 13, 2016
Merged

DidOpenTextDocumentParams does not extend TextDocumentIdentifier#36
dbaeumer merged 1 commit intomicrosoft:masterfrom
Marwes:patch-1

Conversation

@Marwes
Copy link
Copy Markdown
Contributor

@Marwes Marwes commented Jul 9, 2016

@msftclas
Copy link
Copy Markdown

msftclas commented Jul 9, 2016

Hi @Marwes, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@dbaeumer
Copy link
Copy Markdown
Member

@Marwes it does not in the 2.0 version of the protocol anymore. It instead has a property textDocument: TextDocumentItem; which refers to the text document and has additional properties.

@dbaeumer dbaeumer closed this Jul 13, 2016
@Marwes
Copy link
Copy Markdown
Contributor Author

Marwes commented Jul 13, 2016

Sorry, now you got me confused. Is DidOpenTextDocumentParams supposed to extend TextDocumentIdentifier (which gives it an uri field directly in addition to the one in textDocument) but that is not implemented yet in https://github.com/Microsoft/vscode-languageserver-node ?

@dbaeumer
Copy link
Copy Markdown
Member

@Marwes no, it was that way in the 1.0 version of the protocol (which is available here: https://github.com/Microsoft/language-server-protocol/blob/master/versions/protocol-1-x.md). In the 2.0 version we cleaned this up and steps away from 'inlining' parameters.

@Marwes
Copy link
Copy Markdown
Contributor Author

Marwes commented Jul 13, 2016

In that case, should my PR not be a fix since it removes extends TextDocumentIdentifier ?

@dbaeumer
Copy link
Copy Markdown
Member

@Marwes I apologoize a lot. I misread the diff. Makes perfect sense. And thank you for not giving up :-).

@dbaeumer dbaeumer reopened this Jul 13, 2016
@msftclas
Copy link
Copy Markdown

Hi @Marwes, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@dbaeumer dbaeumer merged commit 2d6bc92 into microsoft:master Jul 13, 2016
@Marwes Marwes deleted the patch-1 branch July 13, 2016 15:00
@Marwes
Copy link
Copy Markdown
Contributor Author

Marwes commented Jul 13, 2016

No problem. Just happy to be of some help, the protocol made it really simple to provide completion for my own little language :).

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.

3 participants