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(WebSocketShard): key name in WebSocketShard#_send. #5304

Merged
merged 1 commit into from
Feb 10, 2021

Conversation

BannerBomb
Copy link
Contributor

Please describe the changes this PR makes and why it should be merged:
I just changed an incorrect key name that was introduced in Pull Request #3722. When destroying the websocket from the WebSocketShard#_send method it's using close as the key name instead of closeCode. This was just a small thing that I noticed while going through the files and I did a little bit of testing before I made this pr and it didn't break or solve anything that I know of.

Status and versioning classification:

  • Code changes have been tested against the Discord API, or there are no code changes

I just changed an incorrect key name that was introduced in Pull Request discordjs#3722. When destroying the websocket from the WebSocketShard#_send method it's using `close` as the key name instead of `closeCode`
Copy link
Member

@vladfrangu vladfrangu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why we need TypeScript

@thunder-coding
Copy link

This is why we need TypeScript

What about re-writing Discord.js in v14 after #5106 get's merged

@almostSouji
Copy link
Member

What about re-writing Discord.js in v14 after #5106 get's merged

No.

@iCrawl iCrawl changed the title Changed misspelled key name in WebSocketShard#_send. fix(WebSocketShard): key name in WebSocketShard#_send. Feb 10, 2021
@iCrawl iCrawl merged commit 56d8b44 into discordjs:master Feb 10, 2021
@thunder-coding
Copy link

What about re-writing Discord.js in v14 after #5106 get's merged

No.

Using TypeScript would really benefit the project.

Static Type definitions and everything that makes JavaScript better and secure. We will get enums which will help a lot.

@almostSouji
Copy link
Member

A TypeScript rewrite is planned in a separate repository, it is not versioned yet, so no, v14 will very likely not be the rewrite. Please stop discussing this in a completely unrelated issue, thank you.

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.

6 participants