You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Common between the interfaces is that they have `encode()` and `decode()` methods. The terms "codec" and "encoding" are used interchangeably. Passing these encodings through `Transcoder#encoding()` (which is done implicitly when used in an `abstract-level` database) results in normalized encoding objects that follow [the interface](./lib/encoding.d.ts) of `level-transcoder`.
73
72
@@ -206,7 +205,7 @@ Support us with a monthly donation on [Open Collective](https://opencollective.c
Copy file name to clipboardExpand all lines: UPGRADING.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,8 @@ WIP notes, describing the differences from `level-codec`.
8
8
9
9
- Throws error if encoding is not found, rather than falling back to `id` encoding
10
10
- The `binary` encoding has been renamed to `buffer`, with `binary` as an alias
11
-
- The `utf8` encoding will always return a string. It previously did not touch Buffers. Now it will call `buffer.toString('utf8')` for consistency. Consumers can (selectively) use the `buffer` or `view` encoding to avoid this conversion.
11
+
- The `utf8` encoding previously did not touch Buffers. Now it will call `buffer.toString('utf8')` for consistency. Consumers can use the `buffer` encoding to avoid this conversion.
12
+
- The `id` encoding (aliased as `none`) which wasn't supported by any active `abstract-leveldown` implementation, has been removed.
12
13
- The `ascii`, `ucs2` and `utf16le` encodings are not supported.
0 commit comments