Skip to content

Conversation

@jthemphill
Copy link

Fixes microsoft/typescript-go#2039. Sort of.

Specifically, this creates a test and baseline that documents the correct behavior. From this test, we'll then automatically generate a failing test case in the typescript-go repository. Once we have a failing test case, writing a fix will be fairly easy.

@github-project-automation github-project-automation bot moved this to Not started in PR Backlog Nov 9, 2025
@typescript-bot typescript-bot added the For Uncommitted Bug PR for untriaged, rejected, closed or missing bug label Nov 9, 2025
@typescript-bot
Copy link
Collaborator

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

@jthemphill
Copy link
Author

@microsoft-github-policy-service agree

@jakebailey
Copy link
Member

We don't need to do it like this; we have the ability to create non-generated tests.

@jakebailey jakebailey closed this Nov 10, 2025
@github-project-automation github-project-automation bot moved this from Not started to Done in PR Backlog Nov 10, 2025
@MartinJohns
Copy link
Contributor

we have the ability to create non-generated tests.

Witchcraft!

@jthemphill jthemphill deleted the inlay-hints-tuple-test branch November 11, 2025 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

For Uncommitted Bug PR for untriaged, rejected, closed or missing bug

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Crash in VSCode InlayHint: Unhandled case in Node.ElementList: KindTupleType

4 participants