e4865644c1
I spend some considerable time reverse engineering the module, so I thought I’d write the documentation I would have liked to see. The strategy here is that a user not necessarily has insight into how servant works internally, or even how to write complex servant routes, they just want to generate a list of endpoints and convert the `Req` type into e.g. generated code in $language. Thus, they need to know the semantics of all fields of Req, how they interact and how they relate to a plain http route. I made sure every `f` is replaced with `ftype`, so we have one conventional way of referring to the foreign type argument everywhere. Some enums are not set at all, they are marked as such. `_reqBodyContentType` introduces a major restriction of the module, so that is mentioned in the documentation for now, until the time it will be fixed. A few TODO’s describe places where types don’t make sense but would introduce API-breaking changes, so these should probably be simplified, but bundled in one go. |
||
|---|---|---|
| .. | ||
| src/Servant | ||
| test | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| servant-foreign.cabal | ||
| Setup.hs | ||
servant-foreign
Types and helpers for generating clients for servant servers in arbitrary programming languages.