adding namedroute to index

haskell-servant · Feb 23, 2022 · a9f6190 · a9f6190
1 parent 74b5f06
commit a9f6190
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/doc/cookbook/index.rst b/doc/cookbook/index.rst
@@ -19,6 +19,7 @@ you name it!
 
   structuring-apis/StructuringApis.lhs
   generic/Generic.lhs
+  namedRoutes/NamedRoutes.lhs
   https/Https.lhs
   db-mysql-basics/MysqlBasics.lhs
   db-sqlite-simple/DBConnection.lhs

diff --git a/doc/cookbook/namedRoutes/NamedRoutes.lhs b/doc/cookbook/namedRoutes/NamedRoutes.lhs
@@ -257,7 +257,7 @@ That's it, we have our `MovieCatalogAPI` type!
 
 Let's make a server and a client out of it!
 
-### The Server
+## The Server
 
 As you know, we can’t talk about a server, without addressing the handlers.
 
@@ -377,6 +377,6 @@ Done! We’ve got our client!
 
 We hope that you found this workbook helpful, and that you now feel more confident using the `NamedRoutes` technique.
 
-If you are interested in further understanding the built-in Servant combinators, see [Structuring APIs](https://docs.servant.dev/en/stable/cookbook/structuring-apis/StructuringApis.html).
+If you are interested in further understanding the built-in Servant combinators, see [Structuring APIs](../structuring-apis/StructuringApis.html).
 
 Since `NamedRoutes` is based on the Generic mechanism, you might want to have a look at [Sandy Maguire’s _Thinking with Types_ book](https://doku.pub/download/sandy-maguire-thinking-with-typesz-liborgpdf-4lo5ne7kdj0x).
diff --git a/doc/cookbook/structuring-apis/StructuringApis.lhs b/doc/cookbook/structuring-apis/StructuringApis.lhs
@@ -217,5 +217,6 @@ Servant offers a convenient way to design APIs with records avoiding the orderin
 A simple case is approached in the [Record-based APIs: the simple
 case](https://docs.servant.dev/en/stable/cookbook/generic/Generic.html)
 cookbook, which deals with flat APIs where every endpoint is on the same level.
+
 Also, a more complex example with nested record is discussed in [Record-based APIs: the nested
 records case](TODO) in which we implement an API tree with many branches.