* Expose Flags on MessageEdit and add SuppressEmbeds
Also fix typo in the message flags enum
* Fix deprecation comment
* Add omitempty to Flags member
I wasn't sure if this was going to work but the documentation says:
> The "omitempty" option specifies that the field should be omitted from the encoding if the field has an empty value, defined as false, 0, a nil pointer, a nil interface value, and any empty array, slice, map, or string.
Therefore, if Flags is unmodified it will be omitted.
* Make Components omitempty
I think the null value here may be triggering the "Cannot edit a message authored by another user"
* Remove convenience function for now
* Move deprecated member out of list
Stops the gofmt error
* Fix golint issue
* Change deprecation comment
* feat: code review changes
Co-authored-by: nitroflap <fe.lap.prog@gmail.com>
* feat(endpoints): bumped discord version to 9
* feat: threads barebones
* feat(threads): documentation
* feat(threads): membership caching
* feat(threads): added type to StartThread method
* fix: replaced missing Timestamp definitions with time.Time
* chore: removed debug logs
* chore: removed thread alias for channel type
* feat(webhooks): separated thread option into method
* fix(state): ThreadMembersUpdate member duplication bug
* fix: golint
* feat(threads): pr fixes and BeforeUpdate in ThreadUpdate
* feat: removed unnecessary todo
* feat(state): removed thread last message update in MessageAdd
* Revert "feat(state): removed thread last message update in MessageAdd"
This reverts commit 4ca359fd2cc304e5d0ec2937e25c0c487a1f2096.
* feat(state): update only last message id for thread update
Implements updating message id in MESSAGE_CREATE and MESSAGE_DELETE events. Refer to https://discord.com/developers/docs/topics/gateway#thread-update for more info.
* fix(restapi): passing threadID in WebhookThreadExecute
* feat(state): dropped last_message_id updates for threads
* fix: gofmt
* feat(events#ThreadCreate): added newly_created field
* feat(restapi)!: corrected names of thread functions
* Interactions: context menus
* Example for message context menus
* Added flags to followups
* Example for user context menus
* Godoc fix
* Rebase fix
* Update message types to reflect new separations
Co-authored-by: Carson Hoffman <c@rsonhoffman.com>
* update Activity struct and add emoji functions
* fix the emoji regex
* Remove inline type definitions
* Change function name
* fix message_test function name
* make custom unmarshaljson and change `CreatedAt` to `time.Time`
* fix
Co-authored-by: post <61803796+postrequest69@users.noreply.github.com>
Direct Messages do not have the **guild_id** field for Message Referencing / the new Reply feature.
__Instead it is only **message_id** and **guild_id**__
* Update to API
Updates the golang stuct to current api documentation and adds new util
* Revert of change.
* Update message.go
* Update structs.go
* Yikes this my hand hurts.
* Consistency
* Update message.go
* Bump to v0.17.0
* Add members from GuildMembersChunk to state (#454)
* Revert "Add members from GuildMembersChunk to state (#454)" (#455)
This reverts commit e4487b30d4.
* added clarification when initializing discordgo
from the code I ran on my system with the latest changes this seems to be the syntax for the authentication tokens. I'm guessing it was just never updated.
Let me know if this is incorrect.
Thanks!
* travis: update go versions
* Add Pinned member to message struct
Pinned member was missing.
* Missed an :
* Update README.md
* Removed space
* ContentWithMentionReplaced on roles and nicks (Fixes#208)
* Compatibility
* Like this? 🤔
* More efficient regexp
* Tweaked a little
* Tweaked a little more
* Tweaked even more
* Removed unessecary crap condition that is useless
* Disallow voice channel
* Moved regexp declaration
For compatibility with existing library consumers, the File field is retained but will behave as if Files contained that single file. If both are specified, ChannelMessageSendComplex will return an error.
The message JSON payload is moved to a form-data field called `payload_json`, instead of set in multipart form data. This is supported and the recommended way, as per the API docs.
Apparently, you can attach multiple files if you just name the parts names differently in the multipart request. The parts are named here using the order the files were specified, as `file%d`. This is not documented in the API docs, but definitely works.
This also removes serialization of the File field via json.Marshal, as it will never be directly serialized in the JSON. The new field, Files, is similarly not marshaled.
This additionally adds a ContentType field in File, which can be used to specify the content type of the attached file. The ContentType field will default to setting the header to `application/octet-stream` if empty. Discord currently doesn't do much with the Content-Type header, but we should pass this information along anyway in accordance to the MIME standard.
