31b12d4bf4
This change makes an attempt of abstracting out some of the common functionality found in the handlers for the different request methods. There's still a bit of code duplication between the cases for headers and no headers and empty responses. But it's a significant relative improvement already. |
||
|---|---|---|
| scripts | ||
| servant | ||
| servant-blaze | ||
| servant-client | ||
| servant-docs | ||
| servant-examples | ||
| servant-jquery | ||
| servant-lucid | ||
| servant-server | ||
| .ghci | ||
| .gitignore | ||
| .travis.yml | ||
| README.md | ||
| servant.png | ||
| sources.txt | ||
servant
These libraries provides a family of combinators to define webservices and automatically generate the documentation and client-side querying functions for each endpoint.
In order to minimize the dependencies depending on your needs, we provide these features under different packages.
servant, which contains everything you need to declare a webservice API.servant-server, which lets you implement an HTTP server with handlers for each endpoint of an API.servant-client, which lets you derive automatically Haskell functions that let you query each endpoint of aservantwebservice.servant-docs, which lets you generate API docs for your webservice.servant-jquery, which lets you derive Javascript functions (based on jquery) to query your API's endpoints, in the same spirit asservant-client.servant-blazeandservant-lucidprovide easy HTML rendering of your data as anHTMLcontent-type "combinator".
Tutorial
We have a tutorial guide that introduces the core types and features of servant. After this article, you should be able to write your first servant webservices, learning the rest from the haddocks' examples.