posit-dev / posit-dev/positron
Python parameter completions are incorrectly ordered
Open
Nobody has claimed this yet.
area: completions
bug
lang: python
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
Positron Version:
Positron Version: 2024.06.1 (Universal) build 27
Steps to reproduce the issue:
- Define a function with some params:
def f(b, a): pass - Get param completions:
f(then<Ctrl-Space>. - Completions will be in alphabetical order, but should match the definition.
What did you expect to happen?
Completions should match the definition order.
Were there any error messages in the output or Developer Tools console?
No.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Positron 2024.06.1 with def f(b, a): pass, then inspect the completion path triggered by Ctrl-Space for f(. Done means parameter completions preserve the function definition order instead of appearing alphabetically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100