Skip to content

Conversation

@Dylmay
Copy link
Contributor

@Dylmay Dylmay commented Jun 4, 2024

Currently we do not pass version information when we are publishing diagnostics. See: LSP protocol

Now we pass the version information so the client can create an opinion as to whether the current diagnostics are valid or not for the workspace

@Dylmay
Copy link
Contributor Author

Dylmay commented Jun 4, 2024

There is a versionSupport capability passed by the client which we could check beforehand but the field is optional and we already track the document version so I don't believe there is much reason to change behaviour based on it

Copy link
Member

@ccordoba12 ccordoba12 left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution @Dylmay!

@Dylmay Dylmay requested a review from ccordoba12 June 18, 2024 11:58
@Dylmay
Copy link
Contributor Author

Dylmay commented Jul 8, 2024

@ccordoba12, could I have a re-review please

@ccordoba12
Copy link
Member

Closing and reopening to run our tests again.

@ccordoba12 ccordoba12 closed this Jul 24, 2024
@ccordoba12 ccordoba12 reopened this Jul 24, 2024
@ccordoba12 ccordoba12 added this to the v1.12.0 milestone Jul 24, 2024
Copy link
Member

@ccordoba12 ccordoba12 left a comment

Choose a reason for hiding this comment

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

Thanks @Dylmay for your contribution!

Note: I fixed the errors reported in our Static code analysis workflow in PR #585.

@ccordoba12 ccordoba12 merged commit 9b79576 into python-lsp:develop Jul 24, 2024
@ccordoba12 ccordoba12 added the enhancement New feature or request label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants