typescript-is icon indicating copy to clipboard operation
typescript-is copied to clipboard

Results 49 typescript-is issues
Sort by recently updated
recently updated
newest added

I'm trying to make `typescript-is` work in a Lambda runtime. Lambda is deployed with AWS CDK. `cdk.json`: ``` { "app": "npx ts-node --compiler ttypescript --prefer-ts-exts index.ts", } ``` `package.json`: ```...

remove the `TemplateLiteralPair` type that was moved to `index.d.ts` to fix https://github.com/woutervh-/typescript-is/issues/93#issuecomment-803287815

I've noticed that I've been used this pattern for a while now. It would make a good quality of life improvement if I could check the type and then default...

https://devblogs.microsoft.com/typescript/announcing-typescript-4-4-beta/#symbol-template-signatures Currently it just treats them as a string, but now that typescript 4.4 changes this, it should be changed in typescript-is as well

When using `@AssertType` decoator on `async` methods, calling the method throws synchronously instead of returning rejected promise. example: ```typescript @ValidateClass() export class MessageHandler { async handleMessage(@AssertType() body: { feedId: string...

Would it be possible to support something like that? ```javascript function test(a: T, b: any) { return is(b); // NestedError: Failed to transform node } console.log(test(3, 4)); console.log(test(3, '4')); ```

I want to check the value is a `integer` not `number`. ```typescript type integer = number; interface Test { foo: integer; bar: string; } const isTest(obj: any): obj is Test...

It would be useful to be able to override tsconfig.json `disallowSuperfluousObjectProperties` value on a case by case basis in AssertType decorator factory: `@AssertType({ disallowSuperfluousObjectProperties: true|false})`. Currently I'm pretty sure this...

Types created using type functions with nested props don't work correctly. ``` type CustomType = { bar: { color: Color, }, } type MyType1 = CustomType; type MyType2 = CustomType;...

Just a thought: createAssertType() works perfectly, and we use it for more and more external API calls now (we have hundreds of them). But the lambda which it creates just...