Since I'm currently adding the ability to unfollow or unblock a peer in Peachland, this seemed like a good time to add convenience methods.
I noticed that set_relationship was being unnecessarily noisy, in the sense that it was publishing values that were not technically required (ie. blocking: false when calling follow(peer_id)). I have updated that method to take Option<bool> for following and blocking, instead of simply bool.
unblock(peer_id)
This is a convenience method to publish a contact message with blocking: false.
unfollow(peer_id)
This is a convenience method to publish a contact message with following: false.
Since I'm currently adding the ability to unfollow or unblock a peer in Peachland, this seemed like a good time to add convenience methods.
I noticed that `set_relationship` was being unnecessarily noisy, in the sense that it was publishing values that were not technically required (ie. `blocking: false` when calling `follow(peer_id)`). I have updated that method to take `Option<bool>` for `following` and `blocking`, instead of simply `bool`.
`unblock(peer_id)`
> This is a convenience method to publish a contact message with blocking: `false`.
`unfollow(peer_id)`
> This is a convenience method to publish a contact message with following: `false`.
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.
Since I'm currently adding the ability to unfollow or unblock a peer in Peachland, this seemed like a good time to add convenience methods.
I noticed that
set_relationshipwas being unnecessarily noisy, in the sense that it was publishing values that were not technically required (ie.blocking: falsewhen callingfollow(peer_id)). I have updated that method to takeOption<bool>forfollowingandblocking, instead of simplybool.unblock(peer_id)unfollow(peer_id)