Re: [Specifications] Introduced two new use cases related to API documentation and collection pagination

Review status: 4 of 5 files reviewed at latest revision, 9 unresolved discussions.

---

*[drafts/use-cases/2.1.api-documentation-data-structures.md, line 1 at r1](https://reviewable.io:443/reviews/hydracg/specifications/159#-L7TOIWl3Y1qaNywobmq:-L7YK3ETqc5cWy9GT-9y:b6ntv03) ([raw file](https://github.com/hydracg/specifications/blob/9ec1f3c4b27ee71e17c55325465f43f85e77ffe3/drafts/use-cases/2.1.api-documentation-data-structures.md#L1)):*
<details><summary><i>Previously, alien-mcl (Karol Szczepański) wrote…</i></summary><blockquote>

Done.
</blockquote></details>

Looks like you forgot to push your changes.

---

*[drafts/use-cases/2.1.api-documentation-data-structures.md, line 44 at r1](https://reviewable.io:443/reviews/hydracg/specifications/159#-L7TP-83BXSVMKMmo54r:-L7YK97YzBiiWHJcw1Lo:bw5no1p) ([raw file](https://github.com/hydracg/specifications/blob/9ec1f3c4b27ee71e17c55325465f43f85e77ffe3/drafts/use-cases/2.1.api-documentation-data-structures.md#L44)):*
<details><summary><i>Previously, alien-mcl (Karol Szczepański) wrote…</i></summary><blockquote>

Hmm. Actually I didn't want the documentation to be confused with an actual API resource as other (`/api/event` to not to look to far) are addressed same way. Do we have another option?
</blockquote></details>

What about `/api-documentation` then? It is an actual API resource btw. ;-) A crucial part of its interface

---


*Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/159)*
<!-- Sent from Reviewable.io -->


-- 
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/159#issuecomment-372924824 using your GitHub account

Received on Wednesday, 14 March 2018 07:08:05 UTC