schemas/fssbodysignals: Use StarSystem not SystemName

This matches what's done in other schemas, and allows for use of common
code in EDMC.
This commit is contained in:
Athanasius 2022-05-29 12:36:53 +00:00
parent bad1e3610b
commit 370cef676f
2 changed files with 4 additions and 4 deletions

View File

@ -24,8 +24,8 @@ The primary data source for this schema is the ED Journal event
Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags)
in the Developers' documentation.
#### SystemName
You MUST add a `SystemName` string containing the name of the system from the
#### StarSystem
You MUST add a `StarSystem` string containing the name of the system from the
last `FSDJump`, `CarrierJump`, or `Location` event.
#### StarPos

View File

@ -33,7 +33,7 @@
"type" : "object",
"description" : "Contains all properties from the listed events in the client's journal, minus the Localised strings and the properties marked below as 'disallowed'",
"additionalProperties" : false,
"required" : [ "timestamp", "event", "SystemName", "StarPos", "SystemAddress", "BodyID", "Signals" ],
"required" : [ "timestamp", "event", "StarSystem", "StarPos", "SystemAddress", "BodyID", "Signals" ],
"properties" : {
"timestamp": {
"type" : "string",
@ -50,7 +50,7 @@
"type" : "boolean",
"description" : "Whether the sending Cmdr has an Odyssey expansion."
},
"SystemName": {
"StarSystem": {
"type" : "string",
"minLength" : 1
},