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
Mainly for tests. This way I can add support of signals to
`classic-level` and add tests for it in `abstract-level` that do:
```
if (db.supports.signals?.iterators) {
test('abort', function (t) {
// ..
})
}
```
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -272,6 +272,19 @@ if (db.supports.additionalMethods.foo) {
272
272
273
273
For future extensibility, the properties of `additionalMethods` should be taken as truthy rather than strictly typed booleans. We may add additional metadata (see [#1](https://github.com/Level/supports/issues/1)).
274
274
275
+
### `signals` (object)
276
+
277
+
Which methods or method groups take a `signal` option? At the time of writing there is only one method group: `iterators`. This includes `db.iterator()`, `db.keys()` and `db.values()`. For example:
0 commit comments