fix: resurrect support for compressed text property #342
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.
Way back in PR #35 (a fix for #32), I accidentally disabled support for passing
compressed=True
toTextProperty
. Because #35 involved refactoringTextProperty
so that it no longer inherited fromBlobProperty
, the older version ofTextProperty
needed to be brought back and has now becomeCompressedTextProperty
, which will store text properties as UTF-8 compressed blobs, as was the case with GAE NDB. I've overridden__new__
forTextProperty
so I can substituteCompressedTextProperty
forTextProperty
whencompressed=True
is passed.Fixes #277