test: add leanclient LSP round-trip test for guard diagnostics#1
Merged
Conversation
This PR adds a test that verifies the axiom guard's diagnostics actually reach a language-server client, not just a batch build. It points leanclient at the existing test/consumer project (which loads the guard via plugins := with no import) and asserts the non-standard-axiom warning is published for the declaration depending on the custom axiom. The test is added to test/run.sh and CI gains a uv setup step to run it. The test ensures the consumer is built once first, because the language server elaborates source on its own but cannot load a plugin whose shared library has not yet been compiled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a test that verifies the axiom guard's diagnostics actually reach a language-server client, not just a batch build. It points leanclient at the existing test/consumer project (which loads the guard via
plugins :=with no import) and asserts the non-standard-axiom warning is published for the declaration depending on the custom axiom. The test is wired into test/run.sh and CI gains a uv setup step so it runs across the toolchain matrix.The test builds the consumer once before opening the client: the language server elaborates source on its own, but it cannot load a plugin whose shared library has not yet been compiled (the dynlib is a build artifact), so without that the file fatals before any diagnostic is published. This closes the gap where the diagnostics parser was unit-tested against the guard's message strings but never exercised through a real LSP session.