Proper serialization for chained Event payloads #1725
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.
Calling an
EventHandler
returns anEventSpec
with the function call arguments encoded asVar
.This works fine when formatting the
Var
into an event viaformat.format_event
, however when directly creating a payload and serializing the entireEvent
to send to the client to be queued, thefix_events
function was just taking the "name" of theVar
, which is a json-encoded value.In order to properly serialize the event payload, these
Var
args need to be decoded back into their python values, so that the payload as a whole can be re-serialized properly.Implement a
Var._decode
operation, which operates (mostly) as the inverse ofVar.create
. This is an underscore method, because it actually doesn't return anotherVar
, but instead the real python value that theVar
is created from.Fix #1722
Add/update unit and integration test cases in this area.