Support custom python object serialization #108
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.
Due to security issues we decided to migrate from jinja to mustache and faced some problems with writing custom lambdas. Adding custom serialization of python objects would help a lot.
Toy example, on what is impossible to elegantly achieve now.
data = {"text": "text", "datetime": datetime(2000, 1, 1)}
arrives;received on 2000-01-01T00:00:00: {"text": "text", "datetime": "2000-01-01T00:00:00" }
;data
itself asX
and its JSON representation asY
torender
function as follows:render(data={'X': data, 'Y': json.dumps(data, ...)})
and then use a templatereceived on {{ X.datetime }}: {{ Y }}
. It is clumsy and requires special server-side pre-processing for every such case;Complete example of what we want to achieve:
gives
'03-11-2021: {"dt": "2021-11-03T16:05:29.477125", "text": "text"}'
instead of
"03-11-2021: {'dt': datetime.datetime(2021, 11, 3, 16, 6, 42, 483261), 'text': 'text'}"
without custom serialization.