Rizo

Yeah maps might be tricky. I don't need them for my use-case at the moment, but I'll try to think of something. I'm definitely happy to contribute this if we...

@aantron Hey! :wave: I'm running into a situation where knowing that a client closed a ws connection is critical to implement a product feature. My current approach is to store...

I think at the very least if would be useful to be able to run a clean up function potentially registered with `Dream.websocket ~on_close`.

Are there any workarounds for this?

I wasn't hoping to use it in production, just tried for the sake of curiosity ;)

I'm interested in helping with this. The support for custom extensions would allow us to extract the default values for `apiVersion` and `kind` properties from the `x-kubernetes-group-version-kind` extension field. @rdavison...

@rdavison Looks like your patch is no longer needed. The type annotation for fields is now correctly added by atdgen (fix: https://github.com/mjambon/atd/commit/8089d9e1878b3227ac5fe5d19eee48ced4abcf3a). Update: just noticed this is already [reported](https://github.com/mjambon/atd/issues/172).

Thanks @ostera! I just wanted to state that we are interested in providing first-class support for Reason syntax. In fact I'm currently working on integrating odoc with Reason+esy projects (https://github.com/esy-ocaml/hello-reason/issues/13)....

You haven't shown the most important part – the syntax error in your source code. In any case, I created a simple esy+dune project with `ppx_deriving_yojson`. **package.json:** ```json { "name":...

I will look into the odoc side of things to evaluate how hard it would be to implement this in an automatic way. I agree that, if doable, it would...