versia-pub/docs
2
0
Fork 0
mirror of https://github.com/versia-pub/docs.git synced 2025-12-08 07:18:19 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: 📝 Clarify that Collections should be signed

Browse source
This commit is contained in:
Jesse Wierzbinski 2024-08-06 14:22:17 +02:00
parent 80685555b2
commit df6ba8a59d
No known key found for this signature in database
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
app/structures/collection/page.mdx
View file

@ -9,6 +9,10 @@ Collections are a way to represent paginated groups of entities. They are used e
Pages should be limited to a reasonable number of entities, such as 20 or 80. Pages should be limited to a reasonable number of entities, such as 20 or 80.
<Note>
As Collections are independent and not part of a larger entity (like [ContentFormat](/structures/content-format)), they should have a valid [Signature](/signatures).
</Note>
## Entity Definition ## Entity Definition
<Row> <Row>
@ -36,6 +40,7 @@ Pages should be limited to a reasonable number of entities, such as 20 or 80.
<Property name="prev" type="URI" required={false} typeLink="/types#uri"> <Property name="prev" type="URI" required={false} typeLink="/types#uri">
URI to the previous page of the collection. Query parameters are allowed. URI to the previous page of the collection. Query parameters are allowed.
If there is no previous page, this should be `null`. If there is no previous page, this should be `null`.
</Property> </Property>
<Property name="items" type="Entity[]" required={true}> <Property name="items" type="Entity[]" required={true}>