feat(RESTAPIAttachment): add more properties #1073
Merged
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
almeidx
force-pushed
the
feat/rest-api-attachment-props
branch
from
fdb4ba4 to
f7fad86
Compare
almeidx
force-pushed
the
feat/rest-api-attachment-props
branch
from
f7fad86 to
c3c3e38
Compare
vladfrangu
approved these changes
Aug 23, 2024
This was referenced Sep 21, 2024
This was referenced Sep 24, 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.
Please describe the changes this PR makes and why it should be merged:
The documentation isn't clear about what fields can be sent when creating messages, so I checked the spec and added the missing fields
https://github.com/discord/discord-api-spec/blob/f31843808734a58e4c351fba6fd5768bb480b066/specs/openapi.json#L22778-L22831
Ignored
is_remixsince that field isn't documented at allIf applicable, please reference Discord API Docs PRs or commits that influenced this PR: