Dysnomia port #12
Merged
Dysnomia port #12
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
…abahaha#1383) Co-authored-by: Donovan Daniels <[email protected]>
Co-authored-by: abalabahaha <[email protected]>
Co-authored-by: bsian03 <[email protected]> Co-authored-by: abalabahaha <[email protected]>
Co-authored-by: Donovan Daniels <[email protected]> Co-authored-by: abalabahaha <[email protected]>
…tructure (#8) Also do not pass empty file arrays (triggers data being sent over as multipart data)
* support new trigger metadata types * update trigger type constants * deprecate camel-cased trigger metadata, use raw metadata instead
I believe this should be enough to ensure full forum support. Although, some things might've been missed out by accident.
* Removed editGuildVanity
The vanity endpoint was disabled for bots
```
{
"message": "Bots cannot use this endpoint",
"code": 20001
}
```
* remove Guild#editVanity
* update TSDs appropriately
Co-authored-by: Lars_und_so <[email protected]>
* feat: add new message types currently won't apply any transformations to message content, as I don't know how the messages look like. ref: discord/discord-api-docs@e9711be ref: discord/discord-api-docs@83f6c85 * don't do anything special to the messages right now
* add role connection verification url into OAuthAppInfo
* Add Client#{edit,get}RoleConnectionMetadata
Interface may be subject to change
* add guild connection role tag
* add role connection metadata type enum
* add types
* feat(ThreadChannel): allow fetching more details about thread members * feat(ThreadChannel): add singular thread member fetching * remove redundant parameter * member data from THREAD_MEMBERS_UPDATE is sent in the member field * handle the guild not being cached accordingly * consistently transform options in getThreadMember
* basic role subscription implementation * add role subscription data to Message object see API docs PR 5828 * align guild features with API docs * remove TODO comment roleSubscriptionData will be kept as a camelCased object
taahamahdi
approved these changes
Feb 13, 2023
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.
No description provided.