fix(RESTPostAPIGuildsJSONBody): make some fields nullable #91
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.
This PR makes
afk_channel_id
andsystem_channel_id
inRESTPostAPIGuildsJSONBody
andparent_id
inAPIGuildCreatePartialChannel
nullable.These types are used in the following:
RESTPostAPIGuildsJSONBody
: I tested creating a guild usingPOST /guilds
with anull
afk_channel_id
andsystem_channel_id
, and a channel with a nullparent_id
, and it worked.APITemplate
(viaAPITemplateSerializedSourceGuild
): The example template object in the docs includes anull
afk_channel_id
and a nullparent_id
for a channel. I also tested creating a template from a guild without a system channel and thesystem_channel_id
in the returned template object wasnull
.RESTPostAPIGuildChannelJSONBody
: I tested creating a channel usingPOST /guilds/:id/channels
with a nullparent_id
in the JSON body, and it worked.