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(ClientOptions): make ClientOptions#intents
returns an IntentsBitField
#8617
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is to be standardised, I guess the type when being accessed could be Omit<ClientOptions, "intents"> & { intents: IntentsBitField };
?
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
instead of |
No, here
|
Please double-check the tests! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this need changing too?
this.debug(`[IDENTIFY] Shard ${this.id}/${client.options.shardCount} with intents: ${d.intents}`); |
Previously, this emitted the bit field. However, it now emits the class (IntentsBitField { bitfield: 8192 }
for example). It doesn't seem problematic either way.
so no need to change it? ._. |
ClientOptions#intents
returns an IntentsBitField
Please describe the changes this PR makes and why it should be merged:
I think it's better that
ClientOptions#intents
returns an instance of IntentsBitField instead of just a number.Status and versioning classification: