Add Typescript backend #11
Conversation
chiroptical
force-pushed
the
typescriptBackend
branch
from
6e430c0 to
ff0dcde
Compare
chiroptical
force-pushed
the
typescriptBackend
branch
from
ff0dcde to
b559d8a
Compare
| export type TNewtype = INewtype | ||
|
|
||
| type INewtype = { | ||
| newtypeField: string | number | ||
| } |
There was a problem hiding this comment.
This one is a bit off? How does the JSON look from Aeson for an Either?
|
@chiroptical Curious if Mercury ended up using this, but given the status of this PR I guess not? Is there some other type driven code generation or API specification you're doing to integrate your Haskell and TypeScript code? |
Hey @JBetz, we have not. There are a few reasons for that. Each of our clients (TS, Kotlin, Swift) all have different requirements and it is pretty complicated to share types between all three. Right now, we are using https://hackage.haskell.org/package/aeson-typescript to derive types specifically for TS. They match much closer to 1:1 and the Kotlin/Swift clients are using moat. |
Next step is to try this with the Mercury codebase and see what is broken!