-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
core: handle 004 RPL_MYINFO event #1769
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Itty bitty change-request committee. 🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought I'd already approved this… Sorry for the delay. Must have gotten called away from my previous approval before clicking the button, or something.
Rebased, conflict resolved, and squashed. But I'll have new conflict once #1758 is merged, I know it. |
You can access ISUPPORT information from: * bot.isupport['KEY'] (where KEY is case-insensitive) * bot.KEY when advertised by the server (where KEY is case-sensitive) Co-Authored-By: dgw <dgw@technobabbl.es>
Co-Authored-By: dgw <dgw@technobabbl.es>
This closes #1532 by handling the
RPL_MYINFO
event and storing the info into anamedtuple
. This PR replaces a part of #1536. (see also #1758)