thrift-typescript
thrift-typescript copied to clipboard
creditkarma
Generate TypeScript from Thrift IDL files
For Int64 the generated code is: ``` import Int64 = require("node-int64"); ``` But this syntax is not supported by @babel/plugin-transform-typescript, and I think ``` import Int64 from "node-int64" ``` should...
fixes #173 Currently when resolving const values, identifiers are not resolved recursively, so if identifiers nested inside other ast nodes (eg maps) are used, the may not have been transformed...
We have a map definition with newlines for delimiters and thrift-typescript doesn't like that. ``` const map DATA_TYPE = { -4: 'Notice' -1: 'BackendException' 1: 'GetConnectionId' 2: 'ResolveCountry' // ...etc...
When generating code on Windows, import paths ends up with Windows path separators: ```import * as com_foo_core_thrift from "./..\\..\\..\\..\\core\\thrift";```. This works in Windows, but breaks for anyone trying to run...
I'm not sure what this projects stance is on type helpers, but the output for strict unions is pretty verbose. I am working on a project where we create interfaces...
We've begun work on the next major release of the code generator, focusing on the `thrift-server` target. Some of the new features that will be arriving in some form in...
``` namespace * MyNamespace ``` is recommended in https://www.manning.com/books/programmers-guide-to-apache-thrift-cx (please [ignore the cancelled message](https://github.com/RandyAbernethy/ThriftBook/issues/7)) and compiles fine using the namespace in all languages (that I've tried) using the Apache Thrift...
The int64 constants are being generated incorrectly. ```thrift const i64 BIG_INTEGER = 9223372036854775807 ``` is being emitted as ```typescript export const BIG_INTEGER: Int64 = new Int64(9223372036854776000); ``` As you can...
I'd be very helpful if you'd provide release notes. This would help with fixing bugs and understanding why you should/shouldn't move between versions (like from 1.x to 2.x)
