How to see a fully-expanded TypeScript type without "N more" and "..."?
In VSCode, TypeScript shows really useful expansions of types I define. But there's a limit to what TS will show in IntelliSense. If a type is too long, then I'll see output like this:
Note the "11 more" near the end. Sometimes, for troubleshooting a difficult type definition, it's really helpful to see what's in that "N more" section.
Is there a way to get ahold of (for troubleshooting purposes during development) the fully-expanded type definition, without those "N more" messages to hide what's inside?
https://github.com/Microsoft/vscode/issues/6638 implies that this capability might not have been available (nor planned) as of Feb 2017, but I'm not sure I'm reading that issue correctly and regardless things may have changed in the meantime.
Try setting the noErrorTruncation option to true in tsconfig.json. Confusingly enough, this option affects truncation of types displayed on hover in at least some circumstances; see this issue. Be careful: if your type is really huge, VS Code may hang when you try to view it.
- Elasticsearch curl request not working as expected in Angular 4
- Check type of a function parameter
- Declare and initialize a Dictionary in Typescript
- Angular InjectionToken throws 'No provider for InjectionToken'
- Why doesn't TypeScript enforce async/await on promise?
- Check for browser optional chaining support in Angular project
- Can't use type-fest GreaterThan as parameter type
- My custom-built input component only accepts one character and loses focus from the input field
- Is there a way to get the JSX/TSX of a React component from the code itself?
- How to import an Enum
- How to parameterize a generic function parameter?
- useTemplateRef is not reactive for arrays?
- Using Angular Signals with HostBinding to update style?
- What changes is Mocha waiting for...?
- How to handle undefined values with RenderIf component similar to && check
- Uncaught (in promise) Unable to find element in cloned iframe #2460
- Unit testing Typescript in Visual Studio
- Next.js 14.1 Dev Mode compilation extremely slow
- Does typescript have syntactic sugar around returning a value or throwing an exception if that value is undefined?
- Specify only first type argument
- React with Typescript -- Generics while using React.forwardRef
- How do you configure ESLint's parser and plug-ins using ESLint's flat configuration?
- Unable to use "never" in union compound type
- TypeScript Type-safe Omit Function
- Ways to avoid TypeScript normalizing unions for object literals
- React hooks and comparing object references
- Typescript - wrapping functions while preserving signatures
- How to clear/reset mocks in Vitest
- problem with saving entity that includes another entity
- TypeScript function return type based on input parameter