fc4ca346be
Closes #32159 This PR refines the scope to match just the function name with **the type argument** instead of the whole call expression. Matching to whole call expression prevented methods from expanding inside the function argument. For example, `const foo = bar(someMethod(2)^);` instead of `const foo = bar(someMethod^)`; Follow-up for https://github.com/zed-industries/zed/pull/30312, https://github.com/zed-industries/zed/pull/30351. Mistakenly regressed since https://github.com/zed-industries/zed/pull/31872 when we stopped receiving `insert_range` for this particular case and fallback to `replace_range`. Release Notes: - Fixed issue where code completion in TypeScript function arguments sometimes omitted the dot separator, for example resulting in `NumberparseInt` instead of `Number.parseInt(string)`. --------- Co-authored-by: Michael Sloan <michael@zed.dev> Co-authored-by: Michael Sloan <mgsloan@gmail.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| LICENSE-GPL | ||