forked from martynsmith/node-irc
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch up with bug-fix relevant PRs on node-irc #19
Comments
martynsmith#507 possibly. |
Should probably be closed as #22 is merged. |
@kegsay We haven't merged martynsmith#507 as of yet. |
@chrisdotcode Isn't it an issue (as opposed to a PR)? |
Yeah, good point. It's at least worth keeping in maybe to implement soon. |
I've fixed it in #30, can someone review please? |
Half-Shot
pushed a commit
that referenced
this issue
Feb 23, 2019
Sadly, according to http://defs.ircdocs.horse/defs/numerics.html#err-nochanmodes-477 it looks like error 477 has conflicting usage: - ERR_NOCHANMODES (by RFC2812 spec) - ERR_NEEDREGGEDNICK (with Bahamut, ircu, Unreal) This commit allows codes to just specify a type, instead of also a name, and adds a test to ensure this code is parsed as expected. It also fixes up the order of actual/expected in test-parse-line.js's t.equal calls, and makes the messages more grammatical in context (describe the test, not the success).
Half-Shot
pushed a commit
that referenced
this issue
Feb 23, 2019
Fix issue #19 by adding support for error 477
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following are relevant to us:
The text was updated successfully, but these errors were encountered: