-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fix string completions depending on contextual signatures #52717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix string completions depending on contextual signatures #52717
Conversation
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
//// entry: sendTo((ctx) => ctx.child, { type: "/*2*/" }), | ||
//// }); | ||
|
||
verify.completions({ marker: "1", includes: [`"EVENT"`] }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this one was already working since the omitted node~ was already producing { type: any }
and thus didn't fail the applicability check, whereas when requesting the string completion the type was { type: '' }
and it was failing the check and thus failing to provide the completions
Can you explain what bug is fixed here? Preferably also filing a bug to track the problem. |
tests/cases/fourslash/completionsForStringDependingOnContexSensitiveSignature.ts
Outdated
Show resolved
Hide resolved
tests/cases/fourslash/completionsForStringDependingOnContexSensitiveSignature.ts
Outdated
Show resolved
Hide resolved
…sitiveSignature.ts
fixes #53073
cc @andrewbranch