LSP truncates complex typescript types

[mccraigmccraig]

the deno LSP truncates information from complex typescript types with ... ellipses - i confirmed the same behaviour with both VSCode and emacs

something similar happens with the vanilla typescript LSP - but there is a workaround available, at the possible expense of some performance

it would be great if deno had a similar ability to avoid truncation of type information

[Seally]

Does the noErrorTruncation option in deno.json help (it's already supported)? Or do you need access to the defaultMaximumTruncationLength variable?

[mccraigmccraig]

oh, cool @Seally - in this particular instance noErrorTruncation does work

i strongly suspect that i will also be wanting access to defaultMaximumTruncationLength in the near future though - my types are compounding 😬

[mccraigmccraig]

suspicion confirmed - it didn't take much of a longer type definition before i started seeing truncation again, so i will need access to the defaultMaximumTruncationLength variable to see the full types

(i have confirmed in this particular case that the vanilla typescript LSP with increased defaultMaximumTruncationLength shows me the full type)