LSP highlights wrong argument when using a call as argument
Open
language-server
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 516
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the Bug
In the following code, typing `foo('a', ` will highlight the current argument as b. However, typing `foo(max('a', 'b'), ` will highlight the argument c. It seems like pyrefly simply counts the `,` instead of actual arguments.
Working example when using simple arguments:
Highlighting the wrong argument c:
### Sandbox Link
_No response_
### (Only applicable for extension issues) IDE Information
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.