-
Notifications
You must be signed in to change notification settings - Fork 10
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
New Release #140
Merged
New Release #140
Conversation
This file contains 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
updates: - [github.com/pre-commit/mirrors-mypy: v1.7.0 → v1.7.1](pre-commit/mirrors-mypy@v1.7.0...v1.7.1)
updates: - [github.com/pycqa/isort: 5.12.0 → 5.13.0](PyCQA/isort@5.12.0...5.13.0)
It's important to also check that warnings are *not* raised when they are not valid.
updates: - [github.com/psf/black: 23.11.0 → 23.12.0](psf/black@23.11.0...23.12.0) - [github.com/pycqa/isort: 5.13.0 → 5.13.2](PyCQA/isort@5.13.0...5.13.2)
updates: - [github.com/psf/black: 23.12.0 → 23.12.1](psf/black@23.12.0...23.12.1) - [github.com/pre-commit/mirrors-mypy: v1.7.1 → v1.8.0](pre-commit/mirrors-mypy@v1.7.1...v1.8.0)
- `pygls` no longer depends on `typeguard` - nixpkgs now has recent enough versions of `pygls` and `lsprotocol`
`pytest-lsp` is now packaged with `hatch` and `hatchling`
This way the package's version number should always be in sync
This enables you to build `pytest-lsp` with `nix build ...`. However... this produces a `site-packages` install of `pytest-lsp` so I'm not entirely sure how useful this is...
updates: - [github.com/PyCQA/flake8: 6.1.0 → 7.0.0](PyCQA/flake8@6.1.0...7.0.0)
This gives more control over how items can be formatted.
By providing defaults like `{.|json}` or `{.|json-compact}` we ensure that the `record` command always produces valid JSON
No need to depend on a git snapshot anymore
…Interrupt` This should ensure the command exits cleanly when hitting `Ctrl-C` with an active connection. However, some more investigation is required to determine why it takes multiple `Ctrl-C` attempts to exit.
Aside from just looking cool, this gives the user feedback that the `lsp-devtools record` command is actually doing something.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.