feat: SpaceAPI v15 support
Delete types/v14.go, replace with v15.go.
Rename internal types to not include message version.
I don't currently see the need to support multiple message
versions that have incompatible layouts.
v15 is backwards compatible with v14, so the config example now
specifies both.
Rename the "response" field in the config file to "static" as
dynamic/static makes more sense from the user's perspective.
(Internally it's still SpaceapidConfig.{Dynamic,Response}
to align with type names and usage.)
This commit is contained in:
parent
de506fc8f3
commit
a53a5c3517
10 changed files with 293 additions and 196 deletions
|
|
@ -86,9 +86,9 @@ func ParseConfiguration() (conf SpaceapidConfig) {
|
|||
}
|
||||
}
|
||||
|
||||
// Check if compatible with v14
|
||||
if !slices.Contains(conf.Response.APICompatibility, "14") {
|
||||
log.Fatalln("Provided file doesn't specify compatibility with API version 14")
|
||||
// Sanity check: Config should declare compatibility with current SpaceAPI message version
|
||||
if !slices.Contains(conf.Response.APICompatibility, types.CurrentMessageVersion) {
|
||||
log.Fatalln("Provided config doesn't specify compatibility with current API version", types.CurrentMessageVersion)
|
||||
}
|
||||
|
||||
// Initialize fields for environment sensors
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue