- Fix race condition preventing message listeners from being set.
- Upgraded cabal-core to latest, to bring in hyperswarm changes.
- Fix unhandled promise rejection when initializing a Client instance with a cabal name that can't be resolved. (Handles case of being unable to resolve a key. (#94) (Kira Oakley))
7.3.1 - 2022-05-26
-
Fix crash when creating new PM (Reorder PM null check (#91) (Daniel Chiquito))
The previous ordering would cause an exception even if the null check was triggered.
7.3.0 - 2022-05-24
-
Use getter for PMChannelDetails.joined (#89) (Daniel Chiquito).
The getter refers to the CabalDetails instance which holds the settings for the cabal to determine if the private message channel should be considered joined or not.
This has the side affect of requiring the CabalDetails when initializing the PMChannelDetails, which involves changing the constructor signature.
This is technically a breaking change, however
ChannelDetails
is an internal implementation concern of cabal-details and not intended to be one of the public facing api functions.
- Add methods to read/write a settings file (#89) (Daniel Chiquito)
- Add dependency on js-yaml (#89) (Daniel Chiquito)
- Leaving private messages functionality (#89) (Daniel Chiquito & cblgh)
- Potential issue upstream in cabal-core when receiving ill-formatted PMs (
e6e7308
) (cblgh)
7.2.2 - 2021-12-16
7.2.1 - 2021-12-11
7.2.0 - 2021-11-23
-
bump cabal-core to 15.0.0 (only changes were to pm api) (#82) (@cblgh)
-
disallow channel names == hypercore key, support latest core pm format (#82) (@cblgh)
- A new convention was introduced to limit malicious use in clients: Channel names conforming to the hypercore public key format are forbidden in cabal-client as names for regular channel names (i.e. no channel names that are 64 hex characters)—these are restricted to private channels only (namely: one per person you are chatting with, the name being their public key (or yours, from their perspective))
-
Revert "only add message listener when we're adding a new channel" (
1bf10a9
) (@cblgh).This reverts commit
1dbd522
.It seems this commit introduced a regression in functionality such that messages do not appear in channels (#78) and might also be responsible for a similar bug in [email protected]
It would be good to only add the relevant message listeners, instead of duplicates, but I think it will have to be done anew with fresh eyes.
Adds support for cabal-core's private message:
- a new
CabalDetails.publishPrivateMessage
function has been added CabalDetails.getPrivateMessageList
returns a list of channel names corresponding to ongoing PMs for the local userCabalDetails.isChannelPrivate(channel)
returns true if the passed in channel is a private message channel, false otherwiseCabalDetails.publishMessage
now redirects a published message topublishPrivateMessage
if it is used to post a message to a private message channelpublish-private-message
,private-message
events are now emitted- the
PMChannelDetails
has been added to enable support for private message channels with minimal duplicated functionality CabalDetails.getChannels(opts)
was extended with an optionincludePM
to include private message channels in the returned result- PMs are moderation aware: if you hide a user the channel is hidden and no subsequent PMs will be displayed in your client
For more information, see the API documentation.
7.1.0 - 2021-10-23
- Update Client() docs with opts.aliases and opts.commands (#81) (@ralphtheninja)
7.0.0 - 2021-09-26
The updated version of cabal-core
indirectly contains major changes to the underlying protocol. See the release of [email protected]
for more detailed information.
- Breaking: upgrade
cabal-core
to14.x
(#79) (Lars-Magnus Skog)
6.3.2 - 2021-05-01
This is not the first version, but the first version in this changelog to save some time.