-
Notifications
You must be signed in to change notification settings - Fork 219
Closed
astral-sh/ruff
#22297Labels
completionsBugs or features relating to autocomplete suggestionsBugs or features relating to autocomplete suggestionsserverRelated to the LSP serverRelated to the LSP server
Milestone
Description
Summary
Apologies if this is a duplicate, I couldn't quite tell if this has been included in existing server-labeled issues.
When triggering completions in the scope of method calls, class instantiations, etc, I would expect the argument names to appear first, especially if they are keyword arguments. In reality, Python keywords are ordered first, followed by True/None/False, in-scope symbols, and then the argument names.
Playground link:
https://play.ty.dev/47b0593f-48a0-4c69-85aa-b85d716ab9f7
For comparison, pylance prioritizes the arguments:
And maybe even better, pyrefly shows only the arguments:
Version
ty 0.0.8 (aa7559d 2025-12-29)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
completionsBugs or features relating to autocomplete suggestionsBugs or features relating to autocomplete suggestionsserverRelated to the LSP serverRelated to the LSP server