feat(Presence): Allow bots to set custom status #1475
Merged
Conversation
This file contains 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
bsian03
requested changes
Jan 22, 2024
bsian03
requested changes
Jan 22, 2024
bsian03
requested changes
Jan 22, 2024
bsian03
approved these changes
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Docs reference
WIP. Needs reviewing by a collab to tell me whether they prefer Eris handling it this way, or whether they want me to add anactivities[].stateprop that users specifically need to use to set custom statuses.Changes
activities[].stateprop to use when setting a custom statusBotActivityTypetype from TSdocs, since it is now the same asActivityTypeValidate thetypeprop on all activity objects, rather than just the first one