feat(Guild): add RESTPostAPIGuildBulkBan result and json body
#910
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
ghost
requested review from
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ghost
changed the title
RESTPostAPIGuildBulkBan result and json bodRESTPostAPIGuildBulkBan result and json bodyn bod
ghost
changed the title
RESTPostAPIGuildBulkBan result and json bodyn bodRESTPostAPIGuildBulkBan result and json body
ghost
mentioned this pull request
almeidx
approved these changes
Mar 30, 2024
vladfrangu
approved these changes
Mar 31, 2024
| */ | ||
| export interface RESTPostAPIGuildBulkBanResult { | ||
| /** | ||
| * List of user ids, that were successfully banned |
There was a problem hiding this comment.
Thx discord for random commas
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.
Please describe the changes this PR makes and why it should be merged:
If applicable, please reference Discord API Docs PRs or commits that influenced this PR: