Skip to content

Document name on message interaction metadata object #6734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

advaith1
Copy link
Member

No description provided.

DonovanDMC added a commit to OceanicJS/Oceanic that referenced this pull request Mar 19, 2024
discord/discord-api-docs#6734
Couldn't have been 2 hours earlier, huh. I had to make my release first
@shaydewael shaydewael added the not released This issue or PR is referencing a change that is not yet widely released and/or subject to change. label Mar 26, 2024
@shaydewael
Copy link
Contributor

Right now we're purposefully not documenting name and shouldn't be considered stable. if/when that changes, will follow-up.

@erkinalp
Copy link

erkinalp commented Apr 2, 2024

@shaydewael why not just document as "this field is unstable"?

@yonilerner
Copy link
Member

Ive discussed this in a few places already, but this field is for our specific UI and is subject to change as our UI changes.

@cobaltt7
Copy link

cobaltt7 commented Nov 5, 2024

Would it be possible to document this? The field doesn't seem to have changed, and I find it very useful for my bot to be able to identify the command that triggered a message.

@cobaltt7
Copy link

cobaltt7 commented Dec 9, 2024

hey @shaydewael, sorry for the ping but it's it possible to reconsider this? since again, i find it very useful to have some way to determine what command triggered a message, especially for commands triggered by my own bot

@yonilerner
Copy link
Member

Please open a separate Github discussion for a feature request for determining which command triggered a message send

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not released This issue or PR is referencing a change that is not yet widely released and/or subject to change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants