Micha Reiser

You can create a [project or user level Ruff configuration](https://docs.astral.sh/ruff/configuration/) or specify [a configuration file in VS code](https://docs.astral.sh/ruff/editors/settings/#configuration)

We wouldn't want to hard code the hatch config because it introduces a dependency on hatch itself. Do you know if the hatch default config exists as a toml file...

Oh nice find. Yeah, we don't want to read that because it would require executing or at least parsing python code. I don't see an obvious way on how this...

Thanks for the extra information. I don't think this is something we want to read because it introduces quiet some complexity: * We have to detect that a project is...

Hmm, this might be the case. @dhruvmanila will know better than I.

We discussed this internally. Building the formatter as a linter raised a couple of design questions: * The formatter would need to support `noqa` suppression comments * The `CLI` would...

@shayn-orca I think that's generally right and `check` would probably become the most used command. However, I think there are a couple of workflows that are worth considering: * Let's...

Thanks for the additional logs. Looking at the stack trace, I suspect that the panic happens here because it's the only place where we slice into the string in `to_text_range`:...

> I think having detailed logs involving the request - response messages would be very useful. What positional encoding does your neovim setup use? Is it UTF8 or UTF16?

Thanks. The logs are very useful. I've been able to reproduce the bug with the following unit test: ```rust mod tests { use crate::edit::DocumentVersion; use crate::{PositionEncoding, TextDocument}; use lsp_types::{Position, TextDocumentContentChangeEvent};...