Uh oh!
There was an error while loading. Please reload this page.
Conversation
| | `put` | Key has been updated | `key, value` (any) | | ||
| | `del` | Key has been deleted | `key` (any) | | ||
| | `batch` | Batch has executed | `operations` (array) | | ||
| | `clear` | Entries were deleted | `options` (object) | |
There was a problem hiding this comment.
Not 100% sure about the argument (options). I figured a listener might want to inspect the range options, to find out what was deleted. But that information is not exact (in contrast with the put, del and batch events that tell you exactly which keys were modified).
vweevers
commented
Sep 8, 2019
@ralphtheninja Before we release this I want to think about adding a way to feature-detect it. A module like That db may be |
ralphtheninja
commented
Sep 8, 2019
Maybe we could start by adding a |
vweevers
commented
Sep 8, 2019
Yeah, we could make a patch release on |
vweevers
commented
Sep 8, 2019
It's time for manifests (again), I think. Level/community#42 (comment) |
ralphtheninja
commented
Sep 8, 2019
I was thinking manifest just now :) |
I propose the following timeline:
Edit for the record: it turned out |
Closes#648.
Blocked by Level/deferred-leveldown#72 and Level/encoding-down#89.