Document new features (#207)

- Document `db.getMany(keys)`
- Add `for await...of` example
- Remove notice that `db.supports` isn't (wasn't) widely supported
- Remove notice that `db.clear()` is (was) experimental
- Simplify Promise Support section
- Document `status` in preference over `isXX()` utilities
- Remove redundant API table of contents

Author: vweevers

README.md

@@ -25,11 +25,12 @@
   - [`db.close([callback])`](#dbclosecallback)
   - [`db.put(key, value[, options][, callback])`](#dbputkey-value-options-callback)
   - [`db.get(key[, options][, callback])`](#dbgetkey-options-callback)
+  - [`db.getMany(keys[, options][, callback])`](#dbgetmanykeys-options-callback)
   - [`db.del(key[, options][, callback])`](#dbdelkey-options-callback)
   - [`db.batch(array[, options][, callback])` _(array form)_](#dbbatcharray-options-callback-array-form)
   - [`db.batch()` _(chained form)_](#dbbatch-chained-form)
-  - [`db.isOpen()`](#dbisopen)
-  - [`db.isClosed()`](#dbisclosed)
+  - [`db.status`](#dbstatus)
+  - [`db.isOperational()`](#dbisoperational)
   - [`db.createReadStream([options])`](#dbcreatereadstreamoptions)
   - [`db.createKeyStream([options])`](#dbcreatekeystreamoptions)
   - [`db.createValueStream([options])`](#dbcreatevaluestreamoptions)
@@ -47,7 +48,7 @@
 
 This is a convenience package that:
 
-- exports a function that returns a [`levelup`](https://github.com/Level/levelup#ctor) instance when invoked
+- exports a function that returns a [`levelup`](https://github.com/Level/levelup) instance when invoked
 - bundles the current release of [`leveldown`][leveldown] and [`level-js`][level-js]
 - leverages encodings using [`encoding-down`][encoding-down].
 
@@ -95,25 +96,6 @@ Binary keys and values are supported across the board.
 
 For options specific to [`leveldown`][leveldown] and [`level-js`][level-js] ("underlying store" from here on out), please see their respective READMEs.
 
-- <a href="#ctor"><code><b>level()</b></code></a>
-- <a href="#supports"><code>db.<b>supports</b></code></a>
-- <a href="#open"><code>db.<b>open()</b></code></a>
-- <a href="#close"><code>db.<b>close()</b></code></a>
-- <a href="#put"><code>db.<b>put()</b></code></a>
-- <a href="#get"><code>db.<b>get()</b></code></a>
-- <a href="#del"><code>db.<b>del()</b></code></a>
-- <a href="#batch"><code>db.<b>batch()</b></code></a> _(array form)_
-- <a href="#batch_chained"><code>db.<b>batch()</b></code></a> _(chained form)_
-- <a href="#isOpen"><code>db.<b>isOpen()</b></code></a>
-- <a href="#isClosed"><code>db.<b>isClosed()</b></code></a>
-- <a href="#createReadStream"><code>db.<b>createReadStream()</b></code></a>
-- <a href="#createKeyStream"><code>db.<b>createKeyStream()</b></code></a>
-- <a href="#createValueStream"><code>db.<b>createValueStream()</b></code></a>
-- <a href="#iterator"><code>db.<b>iterator()</b></code></a>
-- <a href="#clear"><code>db.<b>clear()</b></code></a>
-
-<a name="ctor"></a>
-
 ### `db = level(location[, options[, callback]])`
 
 The main entry point for creating a new `levelup` instance.
@@ -161,11 +143,9 @@ level('my-db', { createIfMissing: false }, function (err, db) {
 
 Note that `createIfMissing` is an option specific to [`leveldown`][leveldown].
 
-<a name="supports"></a>
-
 ### `db.supports`
 
-A read-only [manifest](https://github.com/Level/supports). Not [widely supported yet](https://github.com/Level/community/issues/83). Might be used like so:
+A read-only [manifest](https://github.com/Level/supports). Might be used like so:
 
 ```js
 if (!db.supports.permanence) {
@@ -177,42 +157,32 @@ if (db.supports.bufferKeys && db.supports.promises) {
 }
 ```
 
-<a name="open"></a>
-
 ### `db.open([callback])`
 
-Opens the underlying store. In general you should never need to call this method directly as it's automatically called by <a href="#ctor"><code>levelup()</code></a>.
-
-However, it is possible to _reopen_ the store after it has been closed with <a href="#close"><code>close()</code></a>, although this is not generally advised.
+Opens the underlying store. In general you shouldn't need to call this method directly as it's automatically called by [`level()`](#db--levellocation-options-callback). However, it is possible to reopen the store after it has been closed with [`close()`](#dbclosecallback).
 
 If no callback is passed, a promise is returned.
 
-<a name="close"></a>
-
 ### `db.close([callback])`
 
-<code>close()</code> closes the underlying store. The callback will receive any error encountered during closing as the first argument.
+`close()` closes the underlying store. The callback will receive any error encountered during closing as the first argument.
 
 A `levelup` instance has associated resources like file handles and locks. When you no longer need your `levelup` instance (for the remainder of your program) call `close()` to free up resources. The underlying store cannot be opened by multiple instances of `levelup` simultaneously.
 
 If no callback is passed, a promise is returned.
 
-<a name="put"></a>
-
 ### `db.put(key, value[, options][, callback])`
 
-<code>put()</code> is the primary method for inserting data into the store. Both `key` and `value` can be of any type as far as `levelup` is concerned.
+`put()` is the primary method for inserting data into the store. Both `key` and `value` can be of any type as far as `levelup` is concerned.
 
 - `options` is passed on to the underlying store
 - `options.keyEncoding` and `options.valueEncoding` are passed to [`encoding-down`][encoding-down], allowing you to override the key- and/or value encoding for this `put` operation.
 
 If no callback is passed, a promise is returned.
 
-<a name="get"></a>
-
 ### `db.get(key[, options][, callback])`
 
-<code>get()</code> is the primary method for fetching data from the store. The `key` can be of any type. If it doesn't exist in the store then the callback or promise will receive an error. A not-found err object will be of type `'NotFoundError'` so you can `err.type == 'NotFoundError'` or you can perform a truthy test on the property `err.notFound`.
+Get a value from the store by `key`. The `key` can be of any type. If it doesn't exist in the store then the callback or promise will receive an error. A not-found err object will be of type `'NotFoundError'` so you can `err.type == 'NotFoundError'` or you can perform a truthy test on the property `err.notFound`.
 
 ```js
 db.get('foo', function (err, value) {
@@ -234,11 +204,17 @@ db.get('foo', function (err, value) {
 
 If no callback is passed, a promise is returned.
 
-<a name="del"></a>
+### `db.getMany(keys[, options][, callback])`
+
+Get multiple values from the store by an array of `keys`. The optional `options` object is the same as for [`get()`](#dbgetkey-options-callback).
+
+The `callback` function will be called with an `Error` if the operation failed for any reason. If successful the first argument will be `null` and the second argument will be an array of values with the same order as `keys`. If a key was not found, the relevant value will be `undefined`.
+
+If no callback is provided, a promise is returned.
 
 ### `db.del(key[, options][, callback])`
 
-<code>del()</code> is the primary method for removing data from the store.
+`del()` is the primary method for removing data from the store.
 
 ```js
 db.del('foo', function (err) {
@@ -252,11 +228,9 @@ db.del('foo', function (err) {
 
 If no callback is passed, a promise is returned.
 
-<a name="batch"></a>
-
 ### `db.batch(array[, options][, callback])` _(array form)_
 
-<code>batch()</code> can be used for very fast bulk-write operations (both _put_ and _delete_). The `array` argument should contain a list of operations to be executed sequentially, although as a whole they are performed as an atomic operation inside the underlying store.
+`batch()` can be used for fast bulk-write operations (both _put_ and _delete_). The `array` argument should contain a list of operations to be executed sequentially, although as a whole they are performed as an atomic operation inside the underlying store.
 
 Each operation is contained in an object having the following properties: `type`, `key`, `value`, where the _type_ is either `'put'` or `'del'`. In the case of `'del'` the `value` property is ignored. Any entries with a `key` of `null` or `undefined` will cause an error to be returned on the `callback` and any `type: 'put'` entry with a `value` of `null` or `undefined` will return an error.
 
@@ -280,11 +254,9 @@ db.batch(ops, function (err) {
 
 If no callback is passed, a promise is returned.
 
-<a name="batch_chained"></a>
-
 ### `db.batch()` _(chained form)_
 
-<code>batch()</code>, when called with no arguments will return a `Batch` object which can be used to build, and eventually commit, an atomic batch operation. Depending on how it's used, it is possible to obtain greater performance when using the chained form of `batch()` over the array form.
+`batch()`, when called with no arguments will return a `Batch` object which can be used to build, and eventually commit, an atomic batch operation. Depending on how it's used, it is possible to obtain greater performance when using the chained form of `batch()` over the array form.
 
 ```js
 db.batch()
@@ -325,27 +297,19 @@ Commit the queued operations for this batch. All operations not _cleared_ will b
 
 If no callback is passed, a promise is returned.
 
-<a name="isOpen"></a>
-
-### `db.isOpen()`
+### `db.status`
 
-A `levelup` instance can be in one of the following states:
+A readonly string that is one of:
 
-- _"new"_     - newly created, not opened or closed
-- _"opening"_ - waiting for the underlying store to be opened
-- _"open"_    - successfully opened the store, available for use
-- _"closing"_ - waiting for the store to be closed
-- _"closed"_  - store has been successfully closed, should not be used
+- `new`     - newly created, not opened or closed
+- `opening` - waiting for the underlying store to be opened
+- `open`    - successfully opened the store, available for use
+- `closing` - waiting for the store to be closed
+- `closed`  - store has been successfully closed.
 
-`isOpen()` will return `true` only when the state is "open".
+### `db.isOperational()`
 
-<a name="isClosed"></a>
-
-### `db.isClosed()`
-
-`isClosed()` will return `true` only when the state is "closing" _or_ "closed", it can be useful for determining if read and write operations are permissible.
-
-<a name="createReadStream"></a>
+Returns `true` if the store accepts operations, which in the case of `level(up)` means that `status` is either `opening` or `open`, because it opens itself and queues up operations until opened.
 
 ### `db.createReadStream([options])`
 
@@ -383,11 +347,9 @@ You can supply an options object as the first parameter to `createReadStream()`
 
 Underlying stores may have additional options.
 
-<a name="createKeyStream"></a>
-
 ### `db.createKeyStream([options])`
 
-Returns a [Readable Stream](https://nodejs.org/docs/latest/api/stream.html#stream_readable_streams) of keys rather than key-value pairs. Use the same options as described for <a href="#createReadStream"><code>createReadStream</code></a> to control the range and direction.
+Returns a [Readable Stream](https://nodejs.org/docs/latest/api/stream.html#stream_readable_streams) of keys rather than key-value pairs. Use the same options as described for [`createReadStream()`](#dbcreatereadstreamoptions) to control the range and direction.
 
 You can also obtain this stream by passing an options object to `createReadStream()` with `keys` set to `true` and `values` set to `false`. The result is equivalent; both streams operate in [object mode](https://nodejs.org/docs/latest/api/stream.html#stream_object_mode).
 
@@ -404,11 +366,9 @@ db.createReadStream({ keys: true, values: false })
   })
 ```
 
-<a name="createValueStream"></a>
-
 ### `db.createValueStream([options])`
 
-Returns a [Readable Stream](https://nodejs.org/docs/latest/api/stream.html#stream_readable_streams) of values rather than key-value pairs. Use the same options as described for <a href="#createReadStream"><code>createReadStream</code></a> to control the range and direction.
+Returns a [Readable Stream](https://nodejs.org/docs/latest/api/stream.html#stream_readable_streams) of values rather than key-value pairs. Use the same options as described for [`createReadStream()`](#dbcreatereadstreamoptions) to control the range and direction.
 
 You can also obtain this stream by passing an options object to `createReadStream()` with `values` set to `true` and `keys` set to `false`. The result is equivalent; both streams operate in [object mode](https://nodejs.org/docs/latest/api/stream.html#stream_object_mode).
 
@@ -425,17 +385,19 @@ db.createReadStream({ keys: false, values: true })
   })
 ```
 
-<a name="iterator"></a>
-
 ### `db.iterator([options])`
 
-Returns an [`abstract-leveldown` iterator](https://github.com/Level/abstract-leveldown/#iterator), which is what powers the readable streams above. Options are the same as the range options of <a href="#createReadStream"><code>createReadStream</code></a> and are passed to the underlying store.
+Returns an [`abstract-leveldown` iterator](https://github.com/Level/abstract-leveldown/#iterator), which is what powers the readable streams above. Options are the same as the range options of [`createReadStream()`](#dbcreatereadstreamoptions) and are passed to the underlying store.
 
-<a name="clear"></a>
+These iterators support [`for await...of`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for-await...of):
 
-### `db.clear([options][, callback])`
+```js
+for await (const [key, value] of db.iterator()) {
+  console.log(value)
+}
+```
 
-**This method is experimental. Not all underlying stores support it yet. Consult [Level/community#79](https://github.com/Level/community/issues/79) to find out if your (combination of) dependencies support `db.clear()`.**
+### `db.clear([options][, callback])`
 
 Delete all entries or a range. Not guaranteed to be atomic. Accepts the following range options (with the same rules as on iterators):
 
@@ -450,39 +412,14 @@ If no callback is passed, a promise is returned.
 
 ## Promise Support
 
-`level(up)` ships with native `Promise` support out of the box.
-
-Each function taking a callback also can be used as a promise, if the callback is omitted. This applies for:
-
-- `db.get(key[, options])`
-- `db.put(key, value[, options])`
-- `db.del(key[, options])`
-- `db.batch(ops[, options])`
-- `db.batch().write()`
-- `db.clear(options)`
-
-The only exception is the `level` constructor itself, which if no callback is passed will lazily open the underlying store in the background.
+Each function taking a callback can also be used as a promise, if the callback is omitted. The only exception is the `level` constructor itself, which if no callback is passed will lazily open the underlying store in the background.
 
 Example:
 
 ```js
 const db = level('my-db')
-
-db.put('foo', 'bar')
-  .then(function () { return db.get('foo') })
-  .then(function (value) { console.log(value) })
-  .catch(function (err) { console.error(err) })
-```
-
-Or using `async/await`:
-
-```js
-const main = async () => {
-  const db = level('my-db')
-
-  await db.put('foo', 'bar')
-  console.log(await db.get('foo'))
-}
+await db.put('foo', 'bar')
+console.log(await db.get('foo'))
 ```
 
 ## Events