Jane Lewis

For right now, unwrapping the resulting type would probably be your best bet. We don't have a cross-language type definition to wrap `Result` at the moment, but if you think...

> Is this still being worked on? It seems very useful Sorry, this has been put on hold for a while. I'm no longer actively involved with this specific project...

I'd support having a flag in the extension that lets discovered configuration take precedence. We'll look into solving this as we work on configuration for the upcoming VSCode extension based...

It needs another PR, which should be open soon!

### Draft Checklist - [x] Snapshot test output isn't totally correct yet. We need to correctly resolving dangling comments at the end of indented bodies. - [x] A few more...

@a1401358759 Once https://github.com/astral-sh/ruff/pull/11140 lands in the next release, you should be able to specify a custom configuration file! Here's what your LSP config could look like: ```lua return { filetypes...

@MichaReiser I think this is still relevant because we still need to support noqa suppression comments in the new extension, which calls into `ruff_linter` directly. We'll still need to figure...

This PR is really outdated, especially with the major refactors we made to server initialization. I'll re-implement this feature in a new PR that's based off of the latest `main`.

@dhruvmanila > Did you implement the notebook.* variants of the source code actions? No, this still needs to be added. > This might be unrelated to this PR but I'm...

> I think it would be useful to have two separate PRs or commits (whichever you prefer) - one which updates the add_noqa API on the linter side and the...