Allow us to configure the max length of the type hint

[jack-bliss]

• as far as i can tell, this is currently hard-coded here:

https://github.com/orta/vscode-twoslash-queries/blob/d461407faff408be22a776c0c21ffc52799d0a33/src/helpers.ts#L41

• the referenced issue is closed due to inactivity

• this means that sometimes the type hints get cut off long before they're still useable:

• it would be really nice if i could configure this in settings somehow so that i can use more of my screen.
• some people have really really wide monitors; i'm just on a laptop and i'm not using the full extent of the screen

[orta]

I'm open to having it be dynamic (e.g. as long as the current editor) as an optimal answer ( I likely C&P'd the 120 from the TS website codebase) before looking at adding an option

[jack-bliss]

that would probably be ideal tbh! i don't think theres a whole lot of value in truncating it atm, since its always on its own line, and you can only have one per line.

[t6adev]

Happy if it would be not cut off somehow. For now, could we have a configuration to set the length by config?

[BalaM314]

Affected by microsoft/vscode#205708

[ssalbdivad]

Would be a huge help if this were configurable! Even just increasing the default feels like it would be a big help. 120 feels really limiting, especially if you want to use the newer //=>? for same-line inference or just need a longer type name so that you can line up //^? correctly after formatting.

I'd expect that the downside for users whose types get cut off is relatively minor since it would have been truncated either way, but the upside for users with more space is huge 🙏

[tylersayshi]

I'm hoping this helps :)

https://github.com/orta/vscode-twoslash-queries/pull/39