Open MHHukiewitz opened 8 months ago
Can you explain the issue in more details ? I do not understand what the problem is from this short description.
Well, I figured that some functions in connection with messages are too important, to have them spread out around the different repos. IMHO we want:
item_hash
generation process to be contained in this repo as reference for other language implementations (like TypeScript).dump_content
, on which also the item_hash generation process relies.This way we can also write tests for the validators, to make sure that what transformations we implemented here, are working fine with the current message spec.
This branch is mixing unrelated stuff, can you move black
and forbid
to other branches ?
Is the code coverage increasing or at least identical after these changes ? I don't see changes in the tests.
Is the code coverage increasing or at least identical after these changes ? I don't see changes in the tests.
93% -> 92%, due to the decreasing coverage on the utils.py
file from 100% -> 72%. Will increase coverage
In order to avoid mistakes when creating the
item_content
of a message, theextended_json_encoder
has been added from thealeph-sdk-python
package to this central piece of the aleph architecture.Based on #89