Skip to content
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

coretasks: parse RPL_ISUPPORT #1082

Closed
7 tasks done
maxpowa opened this issue May 24, 2016 · 2 comments
Closed
7 tasks done

coretasks: parse RPL_ISUPPORT #1082

maxpowa opened this issue May 24, 2016 · 2 comments

Comments

@maxpowa
Copy link
Contributor

maxpowa commented May 24, 2016

We should parse RPL_ISUPPORT to ensure we're doing the right thing with regards to Identifier parsing (CHANTYPES), account tracking (WHOX/CASEMAPPING), channel permission levels (PREFIX) and so on.

Documentation on individual params http://www.irc.org/tech_docs/005.html
Rough usage statistics http://stats.ircdocs.horse/isupport/

  • network name (NETWORK)
  • privilege prefixes (PREFIX)
  • channel prefixes (CHANTYPES)
  • account tracking (WHOX/CASEMAPPING)
  • multiple NAMES prefixes (NAMESX)
  • maximum message destinations (MAXTARGETS)
    • also target maximums in general (TARGMAX)

All of this and more is parsed and exposed through #1758 and #1769. – @dgw edit

@dgw
Copy link
Member

dgw commented Mar 9, 2019

Hijacked the OP with an edit, sorry @maxpowa. :)

HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Selectively exposes parameters from sopel-irc#1082. Attempts to access parameters
outside of those (whether actually present or not), will issue a
`RuntimeWarning`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Selectively exposes parameters from sopel-irc#1082. Attempts to access parameters
outside of those (whether actually present or not), will issue a
`RuntimeWarning`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Selectively exposes parameters from sopel-irc#1082. Attempts to access parameters
outside of those (whether actually present or not), will issue a
`RuntimeWarning`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 2, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 18, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 18, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 18, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 18, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 23, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there would be parsed into
`bot.server._isupport`.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Apr 23, 2019
`ISUPPORT` parameters can be accessed as `bot.server...`, e.g.,
`bot.server.NAMESX`.

This closes sopel-irc#1082 and closes sopel-irc#1532.
HumorBaby added a commit to HumorBaby/sopel that referenced this issue Jul 31, 2019
Parses one or more `RPL_ISUPPORT` messages from the IRC server for
parameters found in: https://modern.ircdocs.horse/#rplisupport-parameters.

While the documentation above does not explicitly list the parameters
mentioned in sopel-irc#1082, each parameter listed there is in fact parsed into
`bot.server_isupport` if present in the server response.
@dgw
Copy link
Member

dgw commented Dec 12, 2019

Done by @Exirel in #1758 (with a little bonus MYINFO stuff in #1769).

@dgw dgw closed this as completed Dec 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants