Uh oh!
There was an error while loading. Please reload this page.
Fix string completions depending on contextual signatures - #52717
Conversation
TypeScript Bot (typescript-bot)
commented
Feb 10, 2023
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.
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
Nathan Shively-Sanders (sandersn)
commented
Mar 3, 2023
Can you explain what bug is fixed here? Preferably also filing a bug to track the problem. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Mateusz Burzyński (Andarist)
commented
Mar 3, 2023
Nathan Shively-Sanders (@sandersn) filed a new issue here: #53073 |
fixes#53073
cc Andrew Branch (@andrewbranch)