While working on lykin I realised that create_history_stream() was returning messages in the form of SsbMessageValue and not SsbMessageKVT. Returning a KVT provides more flexibility and information; most importantly, it includes the message key.
This PR updates the create_history_stream() method to return a stream of SsbMessageKVT.
I have bumped the minor version (which acts as the major version in our case, since we are still at 0.x.y) to reflect the breaking change of the API.
While working on [lykin](https://git.coopcloud.tech/glyph/lykin) I realised that `create_history_stream()` was returning messages in the form of `SsbMessageValue` and not `SsbMessageKVT`. Returning a KVT provides more flexibility and information; most importantly, it includes the message key.
This PR updates the `create_history_stream()` method to return a stream of `SsbMessageKVT`.
I have bumped the minor version (which acts as the major version in our case, since we are still at `0.x.y`) to reflect the breaking change of the API.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
notplants
While working on lykin I realised that
create_history_stream()was returning messages in the form ofSsbMessageValueand notSsbMessageKVT. Returning a KVT provides more flexibility and information; most importantly, it includes the message key.This PR updates the
create_history_stream()method to return a stream ofSsbMessageKVT.I have bumped the minor version (which acts as the major version in our case, since we are still at
0.x.y) to reflect the breaking change of the API.looks good, can always easily transform sequences of kvts to message values