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

RFC: Initial documentation for the MessageTypes standard #78

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

richteer
Copy link
Contributor

This is very RFC, please do not merge yet!

Included in this document is a table of expected message types. Only a few are defined at the moment, use this PR as a place to discuss which should be included.

@richteer richteer added the RFC label Aug 29, 2017
@richteer richteer requested a review from sjrct August 29, 2017 23:38
@coveralls
Copy link

coveralls commented Aug 29, 2017

Coverage Status

Coverage remained the same at 66.609% when pulling 2537df9 on doc-types into a2e72ba on master.

@coveralls
Copy link

coveralls commented Aug 29, 2017

Coverage Status

Coverage remained the same at 66.609% when pulling aa9caf6 on doc-types into a2e72ba on master.

Message types can be used to control how modules interpret messages. This
file serves as the standard for what are valid types, and how modules or
agents should expect to handle them.
@coveralls
Copy link

coveralls commented Aug 29, 2017

Coverage Status

Coverage remained the same at 66.609% when pulling f04d926 on doc-types into a2e72ba on master.

@sjrct
Copy link
Member

sjrct commented Mar 5, 2019

I think message types or something to that effect should still be a thing, although I don't know if this is the way to do it. Maybe we should use an existing standard like attaching MIME types to messages or something.

@richteer
Copy link
Contributor Author

richteer commented Mar 5, 2019

We sort of use this pattern for help queries though, no? I agree though that I think we should reconsider how we do message typing if we ever want to expand into control messages (get nicknames, kick user, etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants