Alexander Thiemann
Alexander Thiemann
It's too bad that the elm compiler is not published on hackage anymore otherwise we could just use that ast and pretty printer...
See https://github.com/elm-lang/elm-compiler/issues/1300
This looks like a mismatch of the `aeson` `Options`, the `defaultOptions` of `elm-bridge` are not the same `defaultOptions` as in `aeson` (anymore?)... You can fix it by writing something like...
Yes, you can. See https://hackage.haskell.org/package/aeson-1.2.1.0/docs/Data-Aeson.html#v:genericToJSON
Any updates on this @ahri ? Maybe you can contribute a test case?
This alone won't help as we can probably also have mutual recursion. So to fix this we have to add a `_`-function to all object decoders and always use that...
Ah, lazy sounds good!
Right, this is currently not possible due to the fact that `deriveElmDef` generates Elm code that includes the JSON parser/serializer. It sounds like a good change though, would you like...
We are currently piggybacking on the aeson `Options` object, so I think we must wrap it to achieve this level of configuration.
Wow `Servant.Swagger.Test` is cool! In general I use both `hspec` and `HTF`, but current project is using `HTF`. It would be cool to make `Servant.Swagger.Test` testing-framework independent, maybe one could...