@knpkv/clockify-api-client 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,30 @@
1
1
  # @knpkv/clockify-api-client
2
2
 
3
+ ## 1.0.2
4
+
5
+ ### Patch Changes
6
+
7
+ - [#253](https://github.com/knpkv/npm/pull/253) [`521c44e`](https://github.com/knpkv/npm/commit/521c44e9b9d6f4adc3e5ba44f1d9f117698d4442) Thanks [@konopkov](https://github.com/konopkov)! - Update the generated Clockify API client from the latest OpenAPI specification.
8
+
9
+ ## 1.0.1
10
+
11
+ ### Patch Changes
12
+
13
+ - [#249](https://github.com/knpkv/npm/pull/249) [`5a61061`](https://github.com/knpkv/npm/commit/5a610619cef7609148b396d9248924422138221b) Thanks [@konopkov](https://github.com/konopkov)! - Fix `jcf` commands failing to decode Clockify time-entry responses when optional
14
+ fields come back as explicit `null`:
15
+
16
+ - `jcf timer start` failed with `Expected string, got null at ["kioskId"]` —
17
+ Clockify returns `kioskId`, `projectId`, and `taskId` as `null` (not absent).
18
+ - `jcf sync reconcile` failed with `Expected array, got null at [0]["tagIds"]` —
19
+ Clockify returns `tagIds` as `null` for entries with no tags.
20
+
21
+ Patch the OpenAPI spec so those fields decode as nullable across the time-entry
22
+ response schemas (`TimeEntryDtoImplV1`, `TimeEntryDtoV1`,
23
+ `TimeEntryWithRatesDtoV1`) and regenerate the client.
24
+
25
+ Also stop `jcf timer start` from printing a misleading `Timer started` line
26
+ after the start actually failed.
27
+
3
28
  ## 1.0.0
4
29
 
5
30
  ### Major Changes