Closed cce closed 1 year ago
Great! I wasn't sure if removing the paragraph was too drastic. I can do that too
I removed the note — main reason for opening this PR was because I was reading the spec and go-libp2p-pubsub docs at the same time and noticed it wasn't up to date.
I think code organization would be the only difference between preferring a global message_id_fn that checks the topic, vs being able to set per-topic message_id_fn
s ... I found a whole discussion in https://github.com/libp2p/go-libp2p-pubsub/issues/464 about it
This updates an old note in the message ID section of the pubsub spec to reflect that go-libp2p-pubsub currently supports topic-specific message ID configuration, using
WithTopicMessageIdFn
.