We currently have a bug where we don't support futures with optionals for Typescript codegen. In particular,
foo: future<optional<int>> generates a Typescript signature of Promise<number>.
This may have been omitted at the beginning with external types in general. However it works fine to have optional types in ES6 containers like Array/Set/Map (example).
In this PR we update the codegen to take into account the nullability in the TS generator, then add a new test across the languages. CC @LiFengSC
We currently have a bug where we don't support futures with optionals for Typescript codegen. In particular,
foo: future<optional<int>>generates a Typescript signature ofPromise<number>.This may have been omitted at the beginning with external types in general. However it works fine to have optional types in ES6 containers like Array/Set/Map (example).
In this PR we update the codegen to take into account the nullability in the TS generator, then add a new test across the languages. CC @LiFengSC