Test to document the crash in typescript-go#2039#62740
Closed
jthemphill wants to merge 1 commit intomicrosoft:mainfrom
Closed
Test to document the crash in typescript-go#2039#62740jthemphill wants to merge 1 commit intomicrosoft:mainfrom
jthemphill wants to merge 1 commit intomicrosoft:mainfrom
Conversation
typescript-bot
added
the
For Uncommitted Bug
Collaborator
|
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
Author
|
@microsoft-github-policy-service agree |
This was referenced Nov 9, 2025
Member
|
We don't need to do it like this; we have the ability to create non-generated tests. |
Contributor
Witchcraft! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.