Polishing the completion / suggestion

[benbenbang]

Hello team,

Thank you for the great work on Pyrefly! I'm enjoying using it with Zed, and the performance is great.

Feature request: Cleaner completion display

Currently, when I get completions, I'm seeing many overload signatures displayed, which makes them harder to scan quickly. I've noticed that Pyright presents completions in a more concise format. Is improving the completion display (perhaps showing a simplified signature with a way to expand for more details) already on your roadmap?

Question: TAB key for accepting completions

Is there a way to configure Pyrefly to accept completions with the TAB key? Most LSPs I use support this, and it's become part of my muscle memory. If this isn't currently configurable, would it be possible to add support for it?

Thanks again for building such a fast alternative 🙇‍♂️

[grievejia]

Would you mind providing some examples for the overload issue? I'd like to get a more accurate understanding of what exactly the feature ask is -- e.g. what is not displaying right, and what's the desirable outcome.

For TAB completion, I tried Pyrefly-in-Zed as well and TAB did give me completions. My impression was that it's usually a configuration on the editor side, not the language server side. But happy to be corrected if anyone knows which LSP message controls the behavior here.

[kinto0]

thanks for the reports! I don't use zed and it's unfortunate the formatting is like that. filed #1729.

Is it possible to sort the stdlib to be the first one?

very similar to #1685. I'll comment there with this new requirement

I cannot see any signatures

I had started working on this but unfortunately never finished. filed #1728

[benbenbang]

Hello @kinto0

Should I file an issue? Or it's a wonfix

[kinto0]

for which? did I miss making an issue?

[benbenbang]

for which? did I miss making an issue?

I meant all these

[kinto0]

I think I covered all of them. But if my issues don't, please do! thanks again for the reports here