Closed achingbrain closed 6 months ago
I'm not sure this is worth a major bump on it's own, maybe it should be batched up with #468?
Attention: 2 lines
in your changes are missing coverage. Please review.
Comparison is base (
b4e6a8d
) 81.40% compared to head (435e8dd
) 81.42%.
Files | Patch % | Lines |
---|---|---|
src/index.ts | 91.66% | 1 Missing :warning: |
test/compliance.spec.ts | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
People continually mistake the
InsufficientPeers
error for something that can be "worked around" by settingallowPublishToZeroPeers
to true, and they then expect other network nodes to still recieve their messages.This PR renames the option to
allowPublishToZeroTopicPeers
- this makes it clear(er) that it's not that you don't have any peers, it's that no peers you have are listening on the topic.It also improves the JSDoc comment on the option and changes the
Error
message fromPublishError.InsufficientPeers
toPublishError.NoPeersSubscribedToTopic
which (I hope) more accurately describes what's wrong.BREAKING CHANGE: The
allowPublishToZeroPeers
option has been renamed toallowPublishToZeroTopicPeers
Fixes #472