|
71 | 71 |
|
72 | 72 | - feat: make sizeOf public (738b6bf) |
73 | 73 |
|
74 | | - `sizeOf()` was previously just internal, but it is generally useful when |
75 | | - working with Deno KV to be able to estimate the size of keys and values. The |
76 | | - Deno KV documentation currently suggests using the length of |
77 | | - `JSON.stringify()` string, which can be very problematic when dealing with |
78 | | - complex values that don't serialize to JSON but are storable in Deno KV. |
| 74 | + `sizeOf()` was previously just internal, but it is generally useful when working with Deno KV to be able to estimate |
| 75 | + the size of keys and values. The Deno KV documentation currently suggests using the length of `JSON.stringify()` |
| 76 | + string, which can be very problematic when dealing with complex values that don't serialize to JSON but are storable |
| 77 | + in Deno KV. |
79 | 78 |
|
80 | 79 | ## Version 0.20.1 |
81 | 80 |
|
|
85 | 84 |
|
86 | 85 | - feat: arrays, objects, maps and sets are deeply serialized (bf8f285) |
87 | 86 |
|
88 | | - Previously only value supported by JSON directly were serialized as values and |
89 | | - keys of arrays, objects, maps and sets. While kv-toolbox can deserialize the |
90 | | - old format, it supports a new JSON format that allows all value supported by |
91 | | - Deno KV to be properly serialized and deserialized. |
| 87 | + Previously only value supported by JSON directly were serialized as values and keys of arrays, objects, maps and sets. |
| 88 | + While kv-toolbox can deserialize the old format, it supports a new JSON format that allows all value supported by Deno |
| 89 | + KV to be properly serialized and deserialized. |
92 | 90 |
|
93 | 91 | - docs: update changelog (38bd7cd) |
94 | 92 |
|
|
141 | 139 |
|
142 | 140 | - feat: re-work batching for batchedAtomic to align to current Deno KV (e3c8136) |
143 | 141 |
|
144 | | - `batchedAtomic()` now aligns to current versions of Deno KV in how it decides |
145 | | - where to _segment_ atomic transactions. Because of the much higher increases |
146 | | - users should consider only using `batchedAtomic()` when dealing with |
147 | | - potentially large transactions where potentially failing due to the size |
148 | | - restriction is awkward or difficult. |
| 142 | + `batchedAtomic()` now aligns to current versions of Deno KV in how it decides where to _segment_ atomic transactions. |
| 143 | + Because of the much higher increases users should consider only using `batchedAtomic()` when dealing with potentially |
| 144 | + large transactions where potentially failing due to the size restriction is awkward or difficult. |
149 | 145 |
|
150 | 146 | - feat: align blob set and get to Deno.Kv APIs (923faf1) |
151 | 147 |
|
152 | | - **BREAKING** Previously `set()` resolved with void and `get()` resolved with a |
153 | | - value or `null`. In addition, `getMeta()` resolved with a value. |
| 148 | + **BREAKING** Previously `set()` resolved with void and `get()` resolved with a value or `null`. In addition, |
| 149 | + `getMeta()` resolved with a value. |
154 | 150 |
|
155 | | - Now `set()` resolves with a `Deno.KvCommitResult` and `get()` and `getMeta()` |
156 | | - resolve with a `Deno.KvEntryMaybe` with the appropriate type. |
| 151 | + Now `set()` resolves with a `Deno.KvCommitResult` and `get()` and `getMeta()` resolve with a `Deno.KvEntryMaybe` with |
| 152 | + the appropriate type. |
157 | 153 |
|
158 | 154 | - feat: add support for checking blobs in batched_atomic (389730a) |
159 | 155 |
|
160 | | - `batchedAtomic()` transactions now support `.checkBlob()` checks as part of an |
161 | | - atomic transaction. |
| 156 | + `batchedAtomic()` transactions now support `.checkBlob()` checks as part of an atomic transaction. |
162 | 157 |
|
163 | 158 | - feat: add `getAsResponse()` to blob (796ed64) |
164 | 159 |
|
165 | | - `getAsResponse()` will retrieve a blob entry as a `Response` which will stream |
166 | | - the blob from the store to a client. |
| 160 | + `getAsResponse()` will retrieve a blob entry as a `Response` which will stream the blob from the store to a client. |
167 | 161 |
|
168 | 162 | - chore: linting in blob_util (bd6b888) |
169 | 163 | - docs: update readme about batchAtomic (bca0fb6) |
|
0 commit comments