docs: update 'ready' event to 'clientReady' to address deprecation #1114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update documentation to use 'clientReady' instead of the deprecated 'ready' event name, following discord.js v15 changes where 'ready' has been renamed to 'clientReady' to distinguish it from the gateway READY event.
Member
|
@SamHoque Could you please apply that across the entire project? thank you. |
vijayymmeena
reviewed
Oct 2, 2025
| }); | ||
|
|
||
| client.on("ready", async () => { | ||
| client.on("clientReady", async () => { |
Author
Sure, let me go through it! |
Member
|
@SamHoque will you be able to do it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update documentation to use 'clientReady' instead of the deprecated 'ready' event name, following discord.js v15 changes where 'ready' has been renamed to 'clientReady' to distinguish it from the gateway READY event.
Please describe the changes this PR makes: