feat: add CLI check mode - #6
Merged
Merged
Conversation
Run as standalone linter without LSP: java-functional-lsp check File.java java-functional-lsp check --dir src/ java-functional-lsp check src/ tests/ Exits 1 if diagnostics found, 0 if clean. Without 'check' subcommand, starts LSP server as before.
6 tasks
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
2 participants
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.
What
Add standalone CLI check mode so the linter can be run without an LSP client.
Usage
Exits 1 if diagnostics found, 0 if clean. Output format:
path:line:col: [W] rule-id: messageWithout
checksubcommand, starts LSP server as before (backwards compatible).Why
java-functional-lsp checkdirectlyChecklist
uv run ruff check src/ tests/passesuv run mypy src/passesuv run pytestpasses (42 tests, 61% coverage)