monadicsystems/okapi
1
1
Fork 0
mirror of https://github.com/monadicsystems/okapi.git synced 2024-11-23 01:13:38 +03:00
Code Issues Projects Releases Wiki Activity

Polish

Browse Source
This commit is contained in:
Rashad Gover 2023-04-21 09:37:19 +00:00
parent bc2943df7b
commit 9514e22c29
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/index.md
View File

@ -446,7 +446,7 @@ myServer = Server
#### DRY Endpoints
When implementing an API you will usually need the same path to have multiple methods, each with different parameters in the query, body and headers. Since Endpoints are records this is easy to deal with. Let's say we have a typical `/users/{userID : UserID}` route that accepts GET and PUT requests for fetching and updating a specific user respectively. The GET variant doesn't need a Body, but the PUT variant will.
When implementing an API you will usually need the same path to have multiple methods, each with different parameters in the query, body and headers. Since Endpoints are records, this is easy to deal with. Let's say we have a typical `/users/{userID : UserID}` route that accepts GET and PUT requests for fetching and updating a specific user respectively. The GET variant doesn't need a Body, but the PUT variant will.
```haskell
getUser = Endpoint

2
docs/pages/index.html
View File

@ -443,7 +443,7 @@ class="sourceCode haskell"><code class="sourceCode haskell"><span id="cb18-1"><a
<h4>DRY Endpoints</h4>
<p>When implementing an API you will usually need the same path to have
multiple methods, each with different parameters in the query, body and
headers. Since Endpoints are records this is easy to deal with. Let's
headers. Since Endpoints are records, this is easy to deal with. Let's
say we have a typical <code>/users/{userID : UserID}</code> route that
accepts GET and PUT requests for fetching and updating a specific user
respectively. The GET variant doesn't need a Body, but the PUT variant