GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — Write more useful types in `.types` test outputs by rbuckton · Pull Request #48578 · microsoft/TypeScript Conversation
Contributor
#42149 and #42284 improved what we display to users when presenting complex type aliases, but this had the downside of making hundreds of This changes the type writer we use to generate This change makes over a thousand individual tests across over 427
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
With this change in place, how are PRs like the above ones tested/verified to still be working in the future? The two linked PRs are all code changes + |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
The type we use for what the user sees can be verified when it's used in other places. The user never sees We also could leverage fourslash tests for things like verifying quickinfo as well. Traditionally, the .types tests are for us to verify the correct types are being produced, not for reporting what the user sees in the editor. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.