level-supports - npm Package Compare versions

Comparing version 2.0.2 to 2.1.0

CHANGELOG.md

		# Changelog

		## [2.1.0] - 2021-10-27

		### Changed

		- Allow `manifest.encodings` to be an object ([`284e0db`](https://github.com/Level/supports/commit/284e0db)) (Vincent Weevers)

		## [2.0.2] - 2021-10-09
		@@ -42,2 +48,4 @@

		[2.1.0]: https://github.com/Level/supports/releases/tag/v2.1.0

		[2.0.2]: https://github.com/Level/supports/releases/tag/v2.0.2
		@@ -44,0 +52,0 @@

index.js

		@@ -34,3 +34,3 @@ 'use strict'
		streams: manifest.streams \|\| false,
		encodings: manifest.encodings \|\| false,
		encodings: maybeObject(manifest.encodings),
		events: maybeObject(manifest.events),
		@@ -37,0 +37,0 @@

package.json

		{
		"name": "level-supports",
		"version": "2.0.2",
		"version": "2.1.0",
		"description": "Create a manifest describing the abilities of a levelup or abstract-leveldown db",
		@@ -5,0 +5,0 @@ "license": "MIT",

README.md

		@@ -356,6 +356,16 @@ # level-supports

		### `encodings` (boolean)
		### `encodings` (boolean or object)

		Do all relevant db methods take `keyEncoding` and `valueEncoding` options? If true, the db must use a default encoding of utf8 and all its operations must return strings rather than buffers by default.
		Do all relevant db methods take `keyEncoding` and `valueEncoding` options? If truthy, the db must use a default encoding of utf8 and all its operations must return strings rather than buffers by default.

		Support of individual encodings may also be indicated by adding their names as nested properties. For example:

		```js
		{
		encodings: {
		utf8: true
		}
		}
		```

		<details>
		@@ -362,0 +372,0 @@ <summary>Support matrix</summary>

New alerts