support new levelup encoding pattern #6
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in the next release, levelup will support custom encodings.
Level/levelup#149
this pull request means that bytewise can be dropped in to an encoding field as a custom encoding.
The important addition is
buffer: true
which tells levelup to retrive a binary value when doing a read to a custom encoded field.Also, I've added
bytewise-hex
encoding:this is only a few extra lines, but if you need a string, then you need hex.
(base64 is not useful, because order is not consistent)
Currently, this is needed for sublevel - however, soon I will refactor sublevel to support binary keyEncodings.