From af43d4576d5953f966299015adac8e343e9370d0 Mon Sep 17 00:00:00 2001 From: Kris West Date: Thu, 11 Jul 2024 19:13:06 +0100 Subject: [PATCH] Revert timerange changes in 2.0 --- website/static/schemas/2.0/timerange.schema.json | 2 +- website/versioned_docs/version-2.0/context/ref/Chart.md | 6 ++++++ website/versioned_docs/version-2.0/context/ref/TimeRange.md | 6 ++++++ 3 files changed, 13 insertions(+), 1 deletion(-) diff --git a/website/static/schemas/2.0/timerange.schema.json b/website/static/schemas/2.0/timerange.schema.json index 78732e0bf..699c77e24 100644 --- a/website/static/schemas/2.0/timerange.schema.json +++ b/website/static/schemas/2.0/timerange.schema.json @@ -16,7 +16,7 @@ } ], "properties": { - "type": { "const": "fdc3.timeRange" }, + "type": { "const": "fdc3.timerange" }, "startTime": { "type": "string", "format": "date-time" }, "endTime": {"type": "string", "format": "date-time" } }, diff --git a/website/versioned_docs/version-2.0/context/ref/Chart.md b/website/versioned_docs/version-2.0/context/ref/Chart.md index 516ced996..809a31589 100644 --- a/website/versioned_docs/version-2.0/context/ref/Chart.md +++ b/website/versioned_docs/version-2.0/context/ref/Chart.md @@ -25,6 +25,12 @@ https://fdc3.finos.org/schemas/2.0/chart.schema.json ## Details +:::warning + +The `fdc3.timeRange` context type is inconsistently used in FDC3 2.0, occasionally appearing as `fdc3.timerange`. This has been corrected in FDC3 2.1 to always use the camel case form `fdc3.timeRange`. + +::: + | Property | Type | Required | Example Value | |------------------|-----------------|----------|----------------------| | `type` | string | Yes | `'fdc3.chart'` | diff --git a/website/versioned_docs/version-2.0/context/ref/TimeRange.md b/website/versioned_docs/version-2.0/context/ref/TimeRange.md index 9d7b820eb..ac9cc07e2 100644 --- a/website/versioned_docs/version-2.0/context/ref/TimeRange.md +++ b/website/versioned_docs/version-2.0/context/ref/TimeRange.md @@ -31,6 +31,12 @@ Notes: `fdc3.timeRange` +:::warning + +The `fdc3.timeRange` context type is inconsistently used in FDC3 2.0, occasionally appearing as `fdc3.timerange`. This has been corrected in FDC3 2.1 to always use the camel-case form `fdc3.timeRange`. + +::: + ## Schema https://fdc3.finos.org/schemas/2.0/timerange.schema.json