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

fix(Message): #system non-zero message types are not guaranteed to be system #5108

Merged
merged 6 commits into from Dec 12, 2020

Conversation

ckohen
Copy link
Member

@ckohen ckohen commented Dec 12, 2020

As of discord/discord-api-docs#2118 not all non-zero message types are system.
Type 19 Reply is the only current type that benefits from this change.

Note: the reply type will only be recieved once #4879 is implemented.

This PR also introduces SystemMessageTypes so that future message types can be more easily sorted.

Status

  • Code changes have been tested against the Discord API, or there are no code changes
  • I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

  • This PR changes the library's interface (methods or parameters added)
    • This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
  • This PR only includes non-code changes, like changes to documentation, README, etc.

typings/index.d.ts Outdated Show resolved Hide resolved
src/util/Constants.js Outdated Show resolved Hide resolved
ckohen and others added 2 commits December 12, 2020 02:44
Co-authored-by: Jan <66554238+Vaporox@users.noreply.github.com>
@vaporoxx
Copy link
Contributor

oh yeah, you need to add it to Constants too

@iCrawl iCrawl merged commit bb78120 into discordjs:master Dec 12, 2020
@ckohen ckohen deleted the reply-non-system branch December 18, 2020 08:55
@iCrawl iCrawl added this to the Version 13 milestone Jun 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants