-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Incorrect documentation of Scheduled Event's entity_metadata
for STAGE_INSTANCE entity
#4198
Comments
there are currently no plans on publicly supporting this field for events with type STAGE_INSTANCE. this is more of a free form metadata property with no guarantees for this field to be non-null in the future for STAGE_INSTANCE events. Does that help explain the discrepancy or do you still have concerns? |
It does explain the discrepancy but I do feel it would make sense for the documentation to indicate that this field might be an object for events of type STAGE_INSTANCE (especially that it says "This field is required to be null"). It certainly makes sense not to document the |
This was to avoid confusion because e.g. sending a non-null metadata field value for a voice channel event when updating the event will return an error, and doing so for stage events in the future could return an error as well even if it currently might not. |
let me know if that makes sense and you're cool with this issue being closed :) |
Sure |
Description
The Field Requirements By Entity Type table incorrectly states that
entity_metadata
isnull
for entity of type STAGE_INSTANCE.Steps to Reproduce
GET /guilds/{guild.id}/scheduled-events
endpointentity_metadata
is notnull
Expected Behavior
entity_metadata
should benull
or the documentation should state that it is an object.It should also contain information about the fields that can be in that object as the "Guild Scheduled Event Entity Metadata" documentation does not contain
speaker_ids
which is a part ofentity_metadata
for Stage Channels.Current Behavior
entity_metadata
is notnull
despite what documentation states.Screenshots/Videos
None
Client and System Information
Windows 10, Discord Stable client
API requests made through Postman.
The text was updated successfully, but these errors were encountered: