-
Notifications
You must be signed in to change notification settings - Fork 98
test: LSP server verso tests #699
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
base: main
Are you sure you want to change the base?
Conversation
CHANGELOG.md
Outdated
| unreleased | ||
| ---------- | ||
|
|
||
| (Changes that can break existing programs are marked with a "*") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be confusing with Markdown already using * for bulleted lists and boldface. Maybe we should have two headers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We agree to follow what the ref manual does and just write "breaking change" in the changes entry.
|
Summary of PR review discussion with David:
|
I think this one isn't really necessary for a merge here. It's important, but so is avoiding bitrot and getting value from the test that's already here. One or two more should suffice to validate the approach. |
Upstream is happy with this so I'll proceed with that plan. |
9e3f79d to
70158ef
Compare
This avoids spurious infoview display of the internal elaborated constant type. This bug is only observable after applying the fix in leanprover#700 ; will wait for leanprover#700 and leanprover#699 to merge this so we can properly provide a test. Co-authored-by: David Thrane Christiansen <david@lean-fro.org>
We add LSP tests for Verso documents; we reuse the core LSP testing infrastructure from lean4 upstream. See `doc/dev/testing.md` there for more details.
We add LSP tests for Verso documents; we reuse the core LSP testing infrastructure from lean4 upstream. See
doc/dev/testing.mdthere for more details.This is a draft PR, some comments: