From 23edc45fe2d94007ec17c03aea7c55988701b3ae Mon Sep 17 00:00:00 2001 From: akhesaCaro Date: Wed, 23 Feb 2022 07:07:02 +0100 Subject: [PATCH] relative path --- doc/cookbook/generic/Generic.lhs | 2 +- doc/cookbook/namedRoutes/NamedRoutes.lhs | 2 +- doc/cookbook/structuring-apis/StructuringApis.lhs | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/cookbook/generic/Generic.lhs b/doc/cookbook/generic/Generic.lhs index 0156cd313..24463c207 100644 --- a/doc/cookbook/generic/Generic.lhs +++ b/doc/cookbook/generic/Generic.lhs @@ -6,7 +6,7 @@ level. If a you need nesting because you have different branches in your API tree, you might want to jump directly to the [Record-based APIs: the nested records -case](TODO) cookbook that broaches the subject. +case](../namedRoutes/NamedRoutes.html) cookbook that broaches the subject. Shall we begin? diff --git a/doc/cookbook/namedRoutes/NamedRoutes.lhs b/doc/cookbook/namedRoutes/NamedRoutes.lhs index 901461449..17a45a4c0 100644 --- a/doc/cookbook/namedRoutes/NamedRoutes.lhs +++ b/doc/cookbook/namedRoutes/NamedRoutes.lhs @@ -8,7 +8,7 @@ This cookbook explains how to implement such nested-record-based-APIs using `NamedRoutes` through the example of a Movie Catalog. If you don't need the nested aspect of the record-based API, you might want to look at [Record-based APIs: the simple -case](https://docs.servant.dev/en/stable/cookbook/generic/Generic.html) cookbook +case](../generic/Generic.html) cookbook which covers a simpler implementation in which every endpoint is on the same level. diff --git a/doc/cookbook/structuring-apis/StructuringApis.lhs b/doc/cookbook/structuring-apis/StructuringApis.lhs index 6924b19cf..a0e603f0a 100644 --- a/doc/cookbook/structuring-apis/StructuringApis.lhs +++ b/doc/cookbook/structuring-apis/StructuringApis.lhs @@ -37,7 +37,7 @@ endpoints, just like we turn `a * b + a * c` into (It should be noted that the `(:<|>)` operator is not the only way of combining endpoints with Servant. Other techniques are shown in subsequent cookbooks. See -record-based design paragraph) +[record-based alternative for implementing APIs](StructuringApis.html#record-based-alternative-for-implementing-apis)) ``` haskell @@ -215,7 +215,7 @@ It should be noted that the `(:<|>)` is not the only way of combining endpoints. Servant offers a convenient way to design APIs with records avoiding the ordering constraint of the operator. A simple case is approached in the [Record-based APIs: the simple -case](https://docs.servant.dev/en/stable/cookbook/generic/Generic.html) +case](../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. +records case](../namedRoutes/NamedRoutes.html) in which we implement an API tree with many branches.