You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// User defined inside MDX files. We don’t control this.typeProps={someProp: string}// Internal helper type.typeMDXContentProps=Props&{components?: {}}functionMDXContent(props: {readonly[KinkeyofMDXContentProps]: MDXContentProps[K]}){// ^?// The types of props is pretty when hovering over props}MDXContent// ^?// The type of props is ugly when hovering over MDXContent// Can we make this pretty as well? Preferably without introducing intermediate helper types.
🙁 Actual behavior
Hovering over MDXContent shows the type of the props as written.
🙂 Expected behavior
Hovering over MDXContent shows a pretty formatted type of the props, just like TypeScript 5.4.
Bisects to #58078, though reverting it does not seem to actually change this behavior back.
Note that we more or less always want to be writing declarations back as they were written, as that's an invariant to make isolatedDeclarations work. Hover uses the same logic, but at some level this is related to #59029 and whether or not we need a hover mode which tries to do this "prettification".
🔎 Search Terms
“hover”
🕗 Version & Regression Information
⏯ Playground Link
https://www.typescriptlang.org/play/#code/PTAEFUGcFMCdQCbQGYEsB20Gg5VTQBZAEQA1Q0AbaSAOlAHVpEB7dQTAIAXUAYzc9gtKoTgAtUdAFCcAngAdmABUFzIoALygA3pNB7QkFgFtoylnIBcBgRgDmkgL6TJIUAEl0nOOgCGw0dCUCvCyCrTS8swkpADC-NCeZqoaoElqAGTafEZybAmckAD8VloOTpLIAK7oPJyobERkcZ75ABRyKpAlsNA+CGyUMqAA2gDSOOigANbQMizIjbHxiZ0AulbRzV4r5pBjqw4AlNq6+q76F5egAHqFp3quACoBIpFq86AduzhqHdCcslAAHcApNRCwAG5wOygSFwT6dRzOTbLTguMC3dGgZ7MULMD5fZISUCVWyDYGg0DgqGwGFw+AolqeLExHyTIHMIw+GYicS-HoAoY+NQcyiUQqpHrIOA+ABG5KBqDELEq3AwAhYCEqPBh6rgJgQqB8XipgWCrwUUiAA
💻 Code
🙁 Actual behavior
Hovering over
MDXContent
shows the type of theprops
as written.🙂 Expected behavior
Hovering over
MDXContent
shows a pretty formatted type of theprops
, just like TypeScript 5.4.Additional information about the issue
I initially asked for help on Twitter to prettify this, not realizing this was a regression in TypeScript 5.5.
Later in the thread I was asked to report this bug.
The text was updated successfully, but these errors were encountered: