[Doppins] Upgrade dependency irc-upd to 0.8.0 #313
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
A new version was just released of
irc-upd
, so Doppinshas upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!
Upgraded irc-upd from
0.7.0
to0.8.0
Changelog:
Version 0.8.0
Breaking changes:
unhandled
event must not be used to catch specific events – useraw
for that instead. It should be used to handle explicitly events the bot does not do anything with, such as by notifying the user that such an event has occurredraw
event no longer throw, but are caught and passed to theerror
event. As in the documentation, this may still throw if no handler is bound to this event.join
and.part
methods no longer accepts space-separated lists of channels; this caused the bot to send invalid commands to the server. Instead, use comma-separated channel lists, and then the callback will be called for each channel as in the documentationEventEmitter
is now used directly from the require (i.e.var EventEmitter = require('events')
, whereas previouslyvar EventEmitter = require('events').EventEmitter
). This fixes a bug with an atom project using the unforked node-irc version (relevant pull request (https://github.com/martynsmith/node-irc/pull/521
)) but may break compatibility with old versions of node (0.x versions, as those are no longer tested against)New features:
irc.canConvertEncoding()
(aliased toclient.canConvertEncoding()
) to test if the library can convert different encodings with the libraries it's locatedJOIN 0
(which, in the IRC spec, parts from all channels)http://ircv3.net/specs/extensions/sasl-3.1.html
), and if the server does not support SASL, emit on theerror
event – fixes part of#38
(https://github.com/Throne3d/node-irc/issues/38
)Fixed bugs:
debug
config option causes the client not to output when disabled – fixes#34
(https://github.com/Throne3d/node-irc/issues/34
)renickCount
is hit. Previously it would renick to a second nickname and then continue the renicking process – fixes#41
(https://github.com/Throne3d/node-irc/issues/41
)378
on join – fixes part of#38
(https://github.com/Throne3d/node-irc/issues/38
)client.action
splits long messages properly (that is, it still wraps long lines in the CTCP action markers)activateFloodProtection
now disconnects immediately like ifopt.floodProtection
is usedrpl_isupport
in a way that represents its structure better (objects instead of arrays for key-value pairs, and consistently parse values as integers where applicable)names#channel
event when#channel
is mixed-caseclient.disconnect()
join
andpart
even if the server channel differs in case from the one passed toclient.join
orclient.part
Misc:
lib/irc.js
per forkcoveralls
,nyc
)#33
(https://github.com/Throne3d/node-irc/issues/33
)client.activateFloodProtection
should only be called once per instance, not once per connectiontape
tomocha
test.js
irc client REPLhttps://coveralls.io/builds/12716545
) to 94.334% (https://coveralls.io/builds/13502071
)! (#29
(https://github.com/Throne3d/node-irc/issues/29
))