schemas: Journal event template: Couple StarPos instructions

This commit is contained in:
Athanasius committed 2022-01-29 16:56:08 +00:00
1 parent 5f5d0afb29
commit 64dd5832d4
2 files changed
+13 -3

No files matched your search

+3 -2
View File
@@ -48,10 +48,11 @@
data contains a `SystemAddress` value,
2. and a `StarPos` array is *not already present* in the source data.
then you MUST include the `StarPos` section in `Augmentations`.
then you MUST include the `StarPos` section in `Augmentations` and add
`StarPos` to the `required` message properties in the Schema file.
If neither key is in the source data then remove the `StarPos` section from
this document.
this document and the Schema file.
The line:
+10 -1
View File
@@ -30,7 +30,9 @@
# 'messages'. If all you did was remove these comments you would NOT have
# a valid JSON file. You should be adding **at least** one additional
# pertinent 'message' key:value definition.
# 9. You MUST NOT remove the 'disallowed' key, or edit its value. The purpose
# 9. Consult the journalevent-README.md file, particularly the section about
# `StarPos` and remove that section of this file if it is not needed.
# 10. You MUST NOT remove the 'disallowed' key, or edit its value. The purpose
# of this is to be cited as the allowed value on a disallowed key. As it
# defines that the only valid type for the value is **not** any of the
# possible JSON types, its effect is to disallow any value for the key, and
@@ -87,6 +89,13 @@
"type" : "boolean",
"description" : "Boolean value copied from the Journal LoadGame event, when it is present there."
},
"StarPos": {
"type" : "array",
"items" : { "type": "number" },
"minItems" : 3,
"maxItems" : 3,
"description" : "Must be added by the sender"
},
"some_disallowed_key" { "$ref" : "#/definitions/disallowed" },
}
}