Kevin Leung

@francescoagati your linked issue is probably not related. Because tink_json has its own way to serialize haxe enums which is independent of the enum's runtime representation.

> we now allow the type to vary depending on constructor :D I have strong belief in TypeScript that it can handle this with something like: `"White" | {"Rgb": {a:number,...

So I just tried JSON Schema and I think it is expressive enough to describe tink_json's output. ```haxe enum Color { White; Hsl(value:{ hue:Float, saturation:Float, lightness:Float }); Hsv(hsv:{ hue:Float, saturation:Float,...

I made a branch with initial support of json schema: https://github.com/haxetink/tink_json/tree/schema but further work is still needed to support custom rules (`@:json`/`@:jsonStringify`/`@:jsonParse`)

@mdehoog or could you point me to the relevant code sections so I can have a look and prepare a PR?

What is the line limit? Can we just split it while piping?

> we need to be able to set additional headers for every chunk. Ok now it should be able to construct arbitrary parts,

Any chance you can contribute with a PR?

see: https://devzone.nordicsemi.com/f/nordic-q-a/43014/hash-mismatching-when-performing-dfu-over-ble-with-node-js

Not a golang speaker but apparently the implementation is identical there: https://github.com/casbin/casbin/blob/64efe3d122bfe68c9cf68e1bd174173a61f11743/util/util.go#L39