Skip to content

Support encoding/decoding MessagePackTimestamp using non-MessagePack encoders/decoders#56

Open
fumoboy007 wants to merge 1 commit into
hirotakan:masterfrom
fumoboy007:json
Open

Support encoding/decoding MessagePackTimestamp using non-MessagePack encoders/decoders#56
fumoboy007 wants to merge 1 commit into
hirotakan:masterfrom
fumoboy007:json

Conversation

@fumoboy007
Copy link
Copy Markdown

MessagePackTimestamp currently requires a MessagePackEncoder/MessagePackDecoder for encoding/decoding. Using a non-MessagePack encoder/decoder results in a fatal error.

A client may want to use a human-readable serialization format, such as JSON, in automated tests to make it easier to read and write the test. However, if a MessagePackTimestamp is present anywhere in the data structure to be serialized/deserialized, the test will crash.

To enable the above use case, we add fallback behavior for non-MessagePack encoders/decoders when encoding/decoding MessagePackTimestamp.

…k encoders/decoders.

`MessagePackTimestamp` currently requires a `MessagePackEncoder`/`MessagePackDecoder` for encoding/decoding. Using a non-MessagePack encoder/decoder results in a fatal error.

A client may want to use a human-readable serialization format, such as JSON, in automated tests to make it easier to read and write the test. However, if a `MessagePackTimestamp` is present anywhere in the data structure to be serialized/deserialized, the test will crash.

To enable the above use case, we add fallback behavior for non-MessagePack encoders/decoders when encoding/decoding `MessagePackTimestamp`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant