Fix toctree and page titles
commit8990ebb16e89baaa93f8f0f92fc3add52641e788
authorJulian K. Arni <jkarni@gmail.com>
dateWed 27 Jan 2016, 22:58 (11 years ago)
parent8e63078
doc/tutorial/Client.lhs+1−4
@@ -1,7 +1,4 @@
1−---
2−title: Deriving Haskell functions to query an API
3−toc: true
4−---
1+# Deriving Haskell functions to query an API
52
63While defining handlers that serve an API has a lot to it, querying an API is simpler: we do not care about what happens inside the webserver, we just need to know how to talk to it and get a response back. Except that we usually have to write the querying functions by hand because the structure of the API isn't a first class citizen and can't be inspected to generate a bunch of client-side functions.
74
doc/tutorial/Docs.lhs+1−4
@@ -1,7 +1,4 @@
1−---
2−title: Generating documentation from API types
3−toc: true
4−---
1+# Generating documentation from API types
52
63The source for this tutorial section is a literate haskell file, so first we
74need to have some language extensions and imports:
doc/tutorial/Javascript.lhs+1−4
@@ -1,7 +1,4 @@
1−---
2−title: Deriving Javascript functions to query an API
3−toc: true
4−---
1+# Deriving Javascript functions to query an API
52
63We will now see how *servant* lets you turn an API type into javascript
74functions that you can call to query a webservice. The derived code assumes you
doc/tutorial/index.rst+5−5
@@ -61,8 +61,8 @@ Tutorial
6161.. toctree::
6262 :maxdepth: 1
6363
64− api-type.lhs
65− server.lhs
66− client.lhs
67− javascript.lhs
68− docs.lhs
64+ ApiType.lhs
65+ Server.lhs
66+ Client.lhs
67+ Javascript.lhs
68+ Docs.lhs