Enable escaping and unescaping of level parts #13
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.
Description
It is now possible to have arbitrary buffers as levels. So if the buffer has
0x00
or the separator byte, it is no longer a problem. We now automatically escape the separator bytes, and we also automatically escape any escaping byte too0x5c
.Issues Fixed
Tasks
escapeLevel
unescapeLevel
parseKey
to properly handle where0x00
or0x5c
may appear within the level partErrorDBLevelSep
andcheckSepLevelPath
andcheckSepKeyPath
.Final checklist