versia-pub/docs
2
0
Fork 0
mirror of https://github.com/versia-pub/docs.git synced 2025-12-06 14:28:20 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix: clarify ContentFormat numbers for systems languages

Browse source
This commit is contained in:
April John 2024-05-13 17:51:54 +00:00 committed by GitHub
parent 6de1948ac7
commit ee0633f454
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/structures/content-format.md
View file

@ -23,6 +23,7 @@ interface ContentFormat {
} }
} }
``` ```
To maintain compatibility with strongly types languages, numbers MUST fit within a [u64](https://doc.rust-lang.org/std/primitive.u64.html).
Here's an example of how this structure can be used: Here's an example of how this structure can be used:
@ -99,4 +100,4 @@ However, this is not:
Each `ContentFormat` object should be treated as a **single file in multiple optional formats**, not as multiple files. The multiple formats are intended to optimize bandwidth usage. Each `ContentFormat` object should be treated as a **single file in multiple optional formats**, not as multiple files. The multiple formats are intended to optimize bandwidth usage.
If optional fields are provided for one object in the `ContentFormat`, they should be provided for all objects in the `ContentFormat`. For instance, if the `description` field is provided for one object, it should be provided for all objects, as they represent the same file. If optional fields are provided for one object in the `ContentFormat`, they should be provided for all objects in the `ContentFormat`. For instance, if the `description` field is provided for one object, it should be provided for all objects, as they represent the same file.