From 0782ad9e8c3d9797adf1b90920bea16032f3e7c3 Mon Sep 17 00:00:00 2001 From: PondiB Date: Tue, 11 Apr 2023 21:41:34 +0200 Subject: [PATCH 01/16] initialization --- proposals/date_replace.json | 0 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 proposals/date_replace.json diff --git a/proposals/date_replace.json b/proposals/date_replace.json new file mode 100644 index 00000000..e69de29b From d12d47951e328286b8905d2344b47a018d74890c Mon Sep 17 00:00:00 2001 From: PondiB Date: Fri, 14 Apr 2023 11:35:30 +0200 Subject: [PATCH 02/16] date_replace base implementation --- CHANGELOG.md | 1 + meta/implementation.md | 2 +- proposals/date_replace.json | 100 ++++++++++++++++++++++++++++++++++++ 3 files changed, 102 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7d268dd9..4eb13301 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - New processes in proposal state: - `date_difference` + - `date_replace` - `filter_vector` - `flatten_dimensions` - `load_geojson` diff --git a/meta/implementation.md b/meta/implementation.md index 65a24430..4b6c604c 100644 --- a/meta/implementation.md +++ b/meta/implementation.md @@ -67,7 +67,7 @@ options that can be passed to the corresponsing `methods`: - `athmospheric_correction`: `options` - `cloud_detection`: `options` -By default, the parameters don't allow any value except an empty opject. +By default, the parameters don't allow any value except an empty object. Back-ends have to either remove the parameter or define schema to give user details about the supported parameters per supported method. diff --git a/proposals/date_replace.json b/proposals/date_replace.json index e69de29b..1c359f77 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -0,0 +1,100 @@ +{ + "id": "date_replace", + "summary": "Replaces a part of a date", + "description": "Replaces a part of a given date string with a new value based on the provided unit, allowing for easy manipulation of dates.", + "categories": [ + "date & time" + ], + "experimental": true, + "parameters": [ + { + "name": "date", + "description": "The date (and optionally time) to manipulate.\n\nIf the given date doesn't include the time, the process assumes that the time component is `00:00:00Z` (i.e. midnight, in UTC). The millisecond part of the time is optional and defaults to `0` if not given.", + "schema": [ + { + "type": "string", + "format": "date-time", + "subtype": "date-time" + }, + { + "type": "string", + "format": "date", + "subtype": "date" + } + ] + }, + { + "name": "value", + "description": "The period of time in the unit given that is added (positive numbers) or subtracted (negative numbers). The value `0` doesn't have any effect.", + "schema": { + "type": "integer" + } + }, + { + "name": "unit", + "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds - leap seconds are ignored in computations.\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- week: Weeks (equivalent to 7 days)\n- month: Months\n- year: Years\n\nManipulations with the unit `year`, `month`, `week` or `day` do never change the time. If any of the manipulations result in an invalid date or time, the corresponding part is rounded down to the next valid date or time respectively. For example, adding a month to `2020-01-31` would result in `2020-02-29`.", + "schema": { + "type": "string", + "enum": [ + "millisecond", + "second", + "minute", + "hour", + "day", + "week", + "month", + "year" + ] + } + } + ], + "returns": { + "description": "The manipulated date. If a time component was given in the parameter `date`, the time component is returned with the date.", + "schema": [ + { + "type": "string", + "format": "date-time", + "subtype": "date-time" + }, + { + "type": "string", + "format": "date", + "subtype": "date" + } + ] + }, + "examples": [ + { + "arguments": { + "date": "2020-02-01T17:22:45Z", + "value": 6, + "unit": "month" + }, + "returns": "2020-06-01T17:22:45Z" + }, + { + "arguments": { + "date": "2021-03-31T00:00:00+02:00", + "value": 7, + "unit": "day" + }, + "returns": "2021-03-07T00:00:00+02:00" + }, + { + "arguments": { + "date": "2018-01-01", + "value": 2023, + "unit": "year" + }, + "returns": "2023-01-01" + }, + { + "arguments": { + "date": "2018-01-01", + "value": 5, + "unit": "month" + }, + "returns": "2017-05-01" + } + ] +} \ No newline at end of file From 1aaaae1ab633e2bc79846c0c56240fb52ddb2225 Mon Sep 17 00:00:00 2001 From: PondiB Date: Fri, 14 Apr 2023 12:17:17 +0200 Subject: [PATCH 03/16] Update date_replace descriptions --- proposals/date_replace.json | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/proposals/date_replace.json b/proposals/date_replace.json index 1c359f77..93d8f413 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -1,7 +1,7 @@ { "id": "date_replace", "summary": "Replaces a part of a date", - "description": "Replaces a part of a given date string with a new value based on the provided unit, allowing for easy manipulation of dates.", + "description": "Replaces a part of a given date string with a new value based on the provided unit, allowing for easy replacing of dates.", "categories": [ "date & time" ], @@ -9,7 +9,7 @@ "parameters": [ { "name": "date", - "description": "The date (and optionally time) to manipulate.\n\nIf the given date doesn't include the time, the process assumes that the time component is `00:00:00Z` (i.e. midnight, in UTC). The millisecond part of the time is optional and defaults to `0` if not given.", + "description": "The date (and optionally time) to replace.\n\nIf the given date doesn't include the time, the process assumes that the time component is `00:00:00Z` (i.e. midnight, in UTC). The millisecond part of the time is optional and defaults to `0` if not given.", "schema": [ { "type": "string", @@ -25,14 +25,14 @@ }, { "name": "value", - "description": "The period of time in the unit given that is added (positive numbers) or subtracted (negative numbers). The value `0` doesn't have any effect.", + "description": "The period of time in the unit given to replace the existing value.", "schema": { "type": "integer" } }, { "name": "unit", - "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds - leap seconds are ignored in computations.\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- week: Weeks (equivalent to 7 days)\n- month: Months\n- year: Years\n\nManipulations with the unit `year`, `month`, `week` or `day` do never change the time. If any of the manipulations result in an invalid date or time, the corresponding part is rounded down to the next valid date or time respectively. For example, adding a month to `2020-01-31` would result in `2020-02-29`.", + "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the unit `year`, `month` or `day` do never change the time.", "schema": { "type": "string", "enum": [ @@ -41,7 +41,6 @@ "minute", "hour", "day", - "week", "month", "year" ] @@ -49,7 +48,7 @@ } ], "returns": { - "description": "The manipulated date. If a time component was given in the parameter `date`, the time component is returned with the date.", + "description": "The date with replaced value. If a time component was given in the parameter `date`, the time component is returned with the date.", "schema": [ { "type": "string", From b7f125f58e466af1b40b96096c6f904ee3ca9616 Mon Sep 17 00:00:00 2001 From: PondiB Date: Sat, 15 Apr 2023 15:45:29 +0200 Subject: [PATCH 04/16] date_get implelementation --- proposals/date_get.json | 81 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 proposals/date_get.json diff --git a/proposals/date_get.json b/proposals/date_get.json new file mode 100644 index 00000000..1b48b340 --- /dev/null +++ b/proposals/date_get.json @@ -0,0 +1,81 @@ +{ + "id": "date_replace", + "summary": "Gets a part of a date", + "description": "Gets a part of a given date.", + "categories": [ + "date & time" + ], + "experimental": true, + "parameters": [ + { + "name": "date", + "description": "The date (and optionally time) to to get a part of.", + "schema": [ + { + "type": "string", + "format": "date-time", + "subtype": "date-time" + }, + { + "type": "string", + "format": "date", + "subtype": "date" + } + ] + }, + { + "name": "unit", + "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the unit `year`, `month` or `day` do never change the time.", + "schema": { + "type": "string", + "enum": [ + "millisecond", + "second", + "minute", + "hour", + "day", + "month", + "year" + ] + } + } + ], + "returns": { + "description": "Returns a part of date.", + "schema": { + "type": [ + "number" + ] + } + }, + "examples": [ + { + "arguments": { + "date": "2023-02-01T17:22:45Z", + "unit": "month" + }, + "returns": "02" + }, + { + "arguments": { + "date": "2023-03-31T00:00:00+02:00", + "unit": "day" + }, + "returns": "31" + }, + { + "arguments": { + "date": "2023-01-01", + "unit": "year" + }, + "returns": "2023" + }, + { + "arguments": { + "date": "2023-01-01", + "unit": "month" + }, + "returns": "01" + } + ] +} \ No newline at end of file From a05985b5ccb31754fba21d1726d4ff9123800648 Mon Sep 17 00:00:00 2001 From: PondiB Date: Sat, 15 Apr 2023 15:50:43 +0200 Subject: [PATCH 05/16] date_get fix naming issue --- CHANGELOG.md | 1 + proposals/date_get.json | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4eb13301..a325e19c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - New processes in proposal state: - `date_difference` + - `date_get` - `date_replace` - `filter_vector` - `flatten_dimensions` diff --git a/proposals/date_get.json b/proposals/date_get.json index 1b48b340..19e1deaa 100644 --- a/proposals/date_get.json +++ b/proposals/date_get.json @@ -1,5 +1,5 @@ { - "id": "date_replace", + "id": "date_get", "summary": "Gets a part of a date", "description": "Gets a part of a given date.", "categories": [ From 72a639f8ff2593616040b18aa7445da4b8c85798 Mon Sep 17 00:00:00 2001 From: PondiB Date: Sat, 15 Apr 2023 15:58:25 +0200 Subject: [PATCH 06/16] date_get description update --- proposals/date_get.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/date_get.json b/proposals/date_get.json index 19e1deaa..01e716e7 100644 --- a/proposals/date_get.json +++ b/proposals/date_get.json @@ -1,7 +1,7 @@ { "id": "date_get", "summary": "Gets a part of a date", - "description": "Gets a part of a given date.", + "description": "Retrieves a specified portion of a given date object.\n It enables the extraction of specific details from a date object, such as year, month, or day.", "categories": [ "date & time" ], @@ -41,7 +41,7 @@ } ], "returns": { - "description": "Returns a part of date.", + "description": "Returns retrieved portion of a date.", "schema": { "type": [ "number" From c8b4691d444f7042f07989d83f26c979b21a6b68 Mon Sep 17 00:00:00 2001 From: PondiB Date: Mon, 17 Apr 2023 15:08:04 +0200 Subject: [PATCH 07/16] update date_replace and date_get_component based on feedbacks --- ...{date_get.json => date_get_component.json} | 32 ++++++++++--------- proposals/date_replace.json | 18 +++++------ 2 files changed, 26 insertions(+), 24 deletions(-) rename proposals/{date_get.json => date_get_component.json} (61%) diff --git a/proposals/date_get.json b/proposals/date_get_component.json similarity index 61% rename from proposals/date_get.json rename to proposals/date_get_component.json index 01e716e7..ace7454d 100644 --- a/proposals/date_get.json +++ b/proposals/date_get_component.json @@ -1,6 +1,6 @@ { - "id": "date_get", - "summary": "Gets a part of a date", + "id": "date_get_component", + "summary": "Gets a part/component of a date", "description": "Retrieves a specified portion of a given date object.\n It enables the extraction of specific details from a date object, such as year, month, or day.", "categories": [ "date & time" @@ -24,8 +24,8 @@ ] }, { - "name": "unit", - "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the unit `year`, `month` or `day` do never change the time.", + "name": "component", + "description": "The component for the value given. The following pre-defined components are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- day of week: Day of Week\n- day of year: Day of Year\n- week: Weeks (equivalent to 7 days)\n- week number: Week Number\n- month: Months\n- year: Years\n\nReplacements with the component `year`, `month` or `day` do never change the time.", "schema": { "type": "string", "enum": [ @@ -34,6 +34,10 @@ "minute", "hour", "day", + "day of week", + "day of year", + "week", + "week number", "month", "year" ] @@ -43,39 +47,37 @@ "returns": { "description": "Returns retrieved portion of a date.", "schema": { - "type": [ - "number" - ] + "type": "number" } }, "examples": [ { "arguments": { "date": "2023-02-01T17:22:45Z", - "unit": "month" + "component": "month" }, - "returns": "02" + "returns": 2 }, { "arguments": { "date": "2023-03-31T00:00:00+02:00", - "unit": "day" + "component": "day" }, - "returns": "31" + "returns": 31 }, { "arguments": { "date": "2023-01-01", - "unit": "year" + "component": "year" }, - "returns": "2023" + "returns": 2023 }, { "arguments": { "date": "2023-01-01", - "unit": "month" + "component": "month" }, - "returns": "01" + "returns": 1 } ] } \ No newline at end of file diff --git a/proposals/date_replace.json b/proposals/date_replace.json index 93d8f413..efd06fc8 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -1,7 +1,7 @@ { "id": "date_replace", "summary": "Replaces a part of a date", - "description": "Replaces a part of a given date string with a new value based on the provided unit, allowing for easy replacing of dates.", + "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.", "categories": [ "date & time" ], @@ -25,14 +25,14 @@ }, { "name": "value", - "description": "The period of time in the unit given to replace the existing value.", + "description": "The period of time in the component given to replace the existing value.", "schema": { "type": "integer" } }, { - "name": "unit", - "description": "The unit for the value given. The following pre-defined units are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the unit `year`, `month` or `day` do never change the time.", + "name": "component", + "description": "The component for the value given. The following pre-defined components are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the component `year`, `month` or `day` do never change the time.", "schema": { "type": "string", "enum": [ @@ -48,7 +48,7 @@ } ], "returns": { - "description": "The date with replaced value. If a time component was given in the parameter `date`, the time component is returned with the date.", + "description": "The date (and time) with replaced value. If a time component was given in the parameter date, the time component is returned with the date. If the date parameter only includes a date component and a time component is replaced, the resulting output will include the time component as well.", "schema": [ { "type": "string", @@ -67,7 +67,7 @@ "arguments": { "date": "2020-02-01T17:22:45Z", "value": 6, - "unit": "month" + "component": "month" }, "returns": "2020-06-01T17:22:45Z" }, @@ -75,7 +75,7 @@ "arguments": { "date": "2021-03-31T00:00:00+02:00", "value": 7, - "unit": "day" + "component": "day" }, "returns": "2021-03-07T00:00:00+02:00" }, @@ -83,7 +83,7 @@ "arguments": { "date": "2018-01-01", "value": 2023, - "unit": "year" + "component": "year" }, "returns": "2023-01-01" }, @@ -91,7 +91,7 @@ "arguments": { "date": "2018-01-01", "value": 5, - "unit": "month" + "component": "month" }, "returns": "2017-05-01" } From cd514939f0856dbf69ad8d9e0b87e2ce28325e93 Mon Sep 17 00:00:00 2001 From: PondiB Date: Mon, 17 Apr 2023 15:14:28 +0200 Subject: [PATCH 08/16] Update descriptions --- CHANGELOG.md | 2 +- proposals/date_replace.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a325e19c..aa843d0e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - New processes in proposal state: - `date_difference` - - `date_get` + - `date_get_component` - `date_replace` - `filter_vector` - `flatten_dimensions` diff --git a/proposals/date_replace.json b/proposals/date_replace.json index efd06fc8..a114ee69 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -48,7 +48,7 @@ } ], "returns": { - "description": "The date (and time) with replaced value. If a time component was given in the parameter date, the time component is returned with the date. If the date parameter only includes a date component and a time component is replaced, the resulting output will include the time component as well.", + "description": "The date with replaced value. If a time component was given in the parameter date, the time component is returned with the date. If the date parameter only includes a date component and a time component is replaced, the resulting output will include the time component as well.", "schema": [ { "type": "string", From 57427cc896b0de905f51286a52814058ecb9c93d Mon Sep 17 00:00:00 2001 From: PondiB Date: Mon, 17 Apr 2023 18:07:27 +0200 Subject: [PATCH 09/16] reduce white space --- proposals/date_replace.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_replace.json b/proposals/date_replace.json index a114ee69..1d9a0dce 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -48,7 +48,7 @@ } ], "returns": { - "description": "The date with replaced value. If a time component was given in the parameter date, the time component is returned with the date. If the date parameter only includes a date component and a time component is replaced, the resulting output will include the time component as well.", + "description": "The date with replaced value. If a time component was given in the parameter date, the time component is returned with the date. If the date parameter only includes a date component and a time component is replaced, the resulting output will include the time component as well.", "schema": [ { "type": "string", From 4a7ed9dcfa708c8e3bb390bb1649c05e9e0c2111 Mon Sep 17 00:00:00 2001 From: PondiB Date: Fri, 5 May 2023 10:46:57 +0200 Subject: [PATCH 10/16] update descriptions and example for date/time overflows --- proposals/date_replace.json | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/proposals/date_replace.json b/proposals/date_replace.json index 1d9a0dce..18cb2c24 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -1,7 +1,7 @@ { "id": "date_replace", "summary": "Replaces a part of a date", - "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.", + "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\n In case a date/time overflow, the compopent will be clipped to their respetive bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month", "categories": [ "date & time" ], @@ -94,6 +94,15 @@ "component": "month" }, "returns": "2017-05-01" + }, + { + "description": "A date overflow is clipped to the respective bound of the date component.", + "arguments": { + "date": "2023-01-30", + "value": -40, + "component": "day" + }, + "returns": "2023-01-01" } ] } \ No newline at end of file From fab0d9501368a29c4eeff9e7671ba5d68346c7c7 Mon Sep 17 00:00:00 2001 From: PondiB Date: Fri, 5 May 2023 10:50:02 +0200 Subject: [PATCH 11/16] correct wordings' --- proposals/date_replace.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_replace.json b/proposals/date_replace.json index 18cb2c24..8861ba8a 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace.json @@ -1,7 +1,7 @@ { "id": "date_replace", "summary": "Replaces a part of a date", - "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\n In case a date/time overflow, the compopent will be clipped to their respetive bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month", + "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\n In case a date/time overflow, the component will be clipped to their respective bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month", "categories": [ "date & time" ], From 5d5a50f893da622f20edb73487071742a5dd4ca6 Mon Sep 17 00:00:00 2001 From: Brian Pondi Date: Mon, 25 Sep 2023 15:25:13 +0200 Subject: [PATCH 12/16] refactored --- CHANGELOG.md | 2 +- ...place.json => date_replace_component.json} | 36 +++++++++---------- 2 files changed, 19 insertions(+), 19 deletions(-) rename proposals/{date_replace.json => date_replace_component.json} (91%) diff --git a/CHANGELOG.md b/CHANGELOG.md index aa843d0e..d1a2f110 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,7 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 - New processes in proposal state: - `date_difference` - `date_get_component` - - `date_replace` + - `date_replace_component` - `filter_vector` - `flatten_dimensions` - `load_geojson` diff --git a/proposals/date_replace.json b/proposals/date_replace_component.json similarity index 91% rename from proposals/date_replace.json rename to proposals/date_replace_component.json index 8861ba8a..8bb5f4e7 100644 --- a/proposals/date_replace.json +++ b/proposals/date_replace_component.json @@ -1,5 +1,5 @@ { - "id": "date_replace", + "id": "date_replace_component", "summary": "Replaces a part of a date", "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\n In case a date/time overflow, the component will be clipped to their respective bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month", "categories": [ @@ -23,13 +23,6 @@ } ] }, - { - "name": "value", - "description": "The period of time in the component given to replace the existing value.", - "schema": { - "type": "integer" - } - }, { "name": "component", "description": "The component for the value given. The following pre-defined components are available:\n\n- millisecond: Milliseconds\n- second: Seconds .\n- minute: Minutes\n- hour: Hours\n- day: Days - changes only the the day part of a date\n- month: Months\n- year: Years\n\nReplacements with the component `year`, `month` or `day` do never change the time.", @@ -45,6 +38,13 @@ "year" ] } + }, + { + "name": "value", + "description": "The period of time in the component given to replace the existing value.", + "schema": { + "type": "integer" + } } ], "returns": { @@ -66,32 +66,32 @@ { "arguments": { "date": "2020-02-01T17:22:45Z", - "value": 6, - "component": "month" + "component": "month", + "value": 6 }, "returns": "2020-06-01T17:22:45Z" }, { "arguments": { "date": "2021-03-31T00:00:00+02:00", - "value": 7, - "component": "day" + "component": "day", + "value": 7 }, "returns": "2021-03-07T00:00:00+02:00" }, { "arguments": { "date": "2018-01-01", - "value": 2023, - "component": "year" + "component": "year", + "value": 2023 }, "returns": "2023-01-01" }, { "arguments": { "date": "2018-01-01", - "value": 5, - "component": "month" + "component": "month", + "value": 5 }, "returns": "2017-05-01" }, @@ -99,8 +99,8 @@ "description": "A date overflow is clipped to the respective bound of the date component.", "arguments": { "date": "2023-01-30", - "value": -40, - "component": "day" + "component": "day", + "value": -40 }, "returns": "2023-01-01" } From 5391a6a4746ec3a466b31a4d3cf5b87b447de8bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Brian=20P=CF=95ndi?= Date: Tue, 3 Oct 2023 08:16:01 +0200 Subject: [PATCH 13/16] Update proposals/date_get_component.json Co-authored-by: Matthias Mohr --- proposals/date_get_component.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_get_component.json b/proposals/date_get_component.json index ace7454d..354cdd0e 100644 --- a/proposals/date_get_component.json +++ b/proposals/date_get_component.json @@ -9,7 +9,7 @@ "parameters": [ { "name": "date", - "description": "The date (and optionally time) to to get a part of.", + "description": "The date (and optionally time) to get a part of.", "schema": [ { "type": "string", From e2a2793ba0c69cfdd8a016ef63176e64029f472c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Brian=20P=CF=95ndi?= Date: Tue, 3 Oct 2023 08:16:36 +0200 Subject: [PATCH 14/16] Update proposals/date_replace_component.json Co-authored-by: Matthias Mohr --- proposals/date_replace_component.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_replace_component.json b/proposals/date_replace_component.json index 8bb5f4e7..761b4985 100644 --- a/proposals/date_replace_component.json +++ b/proposals/date_replace_component.json @@ -1,7 +1,7 @@ { "id": "date_replace_component", "summary": "Replaces a part of a date", - "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\n In case a date/time overflow, the component will be clipped to their respective bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month", + "description": "Replaces a part of a given date string with a new value based on the provided component, allowing for easy replacing of dates.\n\nIn case a date/time overflow, the component will be clipped to their respective bounds e.g. if hour is set to 27, it can be clipped to 23. Similarly, if day is set to -40, it can be clipped to the first day of the month.", "categories": [ "date & time" ], From 97434394ea29d4631c4842a72d2670a8aca15e91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Brian=20P=CF=95ndi?= Date: Tue, 3 Oct 2023 08:16:48 +0200 Subject: [PATCH 15/16] Update proposals/date_get_component.json Co-authored-by: Matthias Mohr --- proposals/date_get_component.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_get_component.json b/proposals/date_get_component.json index 354cdd0e..6d131ede 100644 --- a/proposals/date_get_component.json +++ b/proposals/date_get_component.json @@ -1,7 +1,7 @@ { "id": "date_get_component", "summary": "Gets a part/component of a date", - "description": "Retrieves a specified portion of a given date object.\n It enables the extraction of specific details from a date object, such as year, month, or day.", + "description": "Retrieves a specified portion of a given date object.\nIt enables the extraction of specific details from a date object, such as year, month, or day.", "categories": [ "date & time" ], From 770962a59cc24a455bc7830c0fdd28498592add8 Mon Sep 17 00:00:00 2001 From: Brian Pondi Date: Wed, 3 Jan 2024 14:50:59 +0100 Subject: [PATCH 16/16] refactor --- proposals/date_get_component.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/date_get_component.json b/proposals/date_get_component.json index 6d131ede..5013a16e 100644 --- a/proposals/date_get_component.json +++ b/proposals/date_get_component.json @@ -1,7 +1,7 @@ { "id": "date_get_component", "summary": "Gets a part/component of a date", - "description": "Retrieves a specified portion of a given date object.\nIt enables the extraction of specific details from a date object, such as year, month, or day.", + "description": "Retrieves a specified portion of a given date.\nIt enables the extraction of specific details from a date, such as year, month, or day.", "categories": [ "date & time" ],