Kyle Into

pyright seems like it uses [depth](https://github.com/microsoft/pyright/blob/5f7ce347e8fbf80c826870b4a95395916cce3454/packages/pyright-internal/src/languageService/autoImporter.ts#L496)(number of dots) to compare these. then pyright also uses [MRU ](https://github.com/microsoft/pyright/blob/5f7ce347e8fbf80c826870b4a95395916cce3454/packages/pyright-internal/src/languageService/completionProvider.ts#L212)to put recent auto imports at the top I bet a combination of these...

thank you for the report! would you be able to share the version of textual you are using and how you installed it into your environment? how is your project...

> `textual>=6.6.0` and yes the correct interpreter is selected, the ty extension displays these properly. this is likely an issue with us not finding the correct source code. would you...

> The reason it's important to me is to be able to "discard" outdated diagnostics with an old version in case they are returned after a new version is published....

> I've implemented the **pull model** (where unopened files are analyzed when `textDocument/diagnostic` is explicitly requested for them, which is what the tests do). > I think it's necessary to...

All of the tests seem to be based on document_diagnostic: but doesn't actually test the behavior, since the language server operates on publishDiagnostics in the IDE. you should remove the...

> Thanks for the review and suggestions! Would you like me to handle the follow-up items (documentation + renaming to "project" mode) in separate PRs???? sure, if you want, that'd...

I'm sorry about this falling through this week. There's a few things that have to happen: - merge conflicts - centralize logic in one place I attempted this but ran...

> https://github.com/user-attachments/assets/de15aba9-f811-4a1c-93b4-3820e5b4b88a > > As you can see in the video attached, > auto suggestions such as keyword suggestions, variable name suggestion etc. was working before installing pyrefly, but after...

thanks for the report! this is fixed in `0.16.1`: please make sure your extension is fully updated. If there's issues, feel free to reopen this issue