Fix encoding/decoding for OrjsonField #61
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.
The encoder and decoder are expected to be objects following the
JSONEncoder
andJSONDecoder
interfaces, respectively. Thus, the orjsondumps
andloads
functions cannot be used directly.Define
JSONEncoder
andJSONDecoder
subclasses which wrap orjson, and use these as the encoder and decoder forOrjsonField
.This field was only used by the
/api/notification_settings/
settings endpoint, so that endpoint should now be able to work. Previously, it always reported a JSON validation error for thecondition
field. To test it, the following code can be used