It looks like you are wanting to verify that handleError gets called when build runs. Private methods are compiled to normal JavaScript prototype methods, so you can use the any type to let the spy creation pass through the TypeScript type checking. Here is a highly simplified example: class OrderBuilder { public build() { this.handleError() … Read more
this is my solution const url = this.router.serializeUrl(this.router.createUrlTree([‘/my/url/route’], { queryParams: { …anyQueryParamsYouWantOrOmitThis } })); window.open(url, ‘_blank’);
The type of this.previousPieceSelected is inferred from the initial state, and it’s currently initialized to undefined, so it thus has a type of undefined (meaning it can only be assigned a value of undefined). Use type assertion on the initial undefined value (i.e., the as keyword plus the desired type of Piece | undefined). Also … Read more
I had this same problem and realize that despite of no having errors on my IDE, the error was still thrown so I just Restart the server and it works perfectly… I have to do this every time I created a import or export anything with TS.
Alternatively, use “skipLibCheck”: true in the compiler options.
You can’t specify types for function declarations. You can only use Parameters and ReturnType. The only minor improvement would be to use destructuring for the parameters: type Add = (x:number, y:number) => number function add(…[x, y]: Parameters<Add>): ReturnType<Add> { return x + y; } Playground Link
TypeScript Playground isn’t a fully fledged sandbox solution. It’s merely meant as a simple type explorer that doesn’t need dependencies. For your use case I would recommend using CodeSandbox instead. It comes with a whole bunch of TypeScript templates to choose from when creating a sandbox. TypeScript Playground also has an export menu where you … Read more
You want something like partial type parameter inference, which is not currently a feature of TypeScript (see microsoft/TypeScript#26242). Right now you either have to specify all type parameters manually or let the compiler infer all type parameters; there’s no partial inference. As you’ve noticed, generic type parameter defaults do not scratch this itch; a default … Read more
You can do it with NonNullable<T>, but not as a constraint on the type-parameters, but using it as an interface-type on get‘s R, like so: function get<K, R>( o: { get: (key: K) => NonNullable<R> }, key: K ): NonNullable<R> { return o.get(key); } So this code gives me an error: const params = new … Read more
You need to provide a constraint for your generic type as follows: <T extends { id?: string }> Update the line const updateArrayOfObjects = <T>(arrayOfObjects: T[], newObject: T, deleteObject: boolean = false): T[] => { to const updateArrayOfObjects = <T extends { id?: string }>(arrayOfObjects: T[], newObject: T, deleteObject: boolean = false): T[] => {