Document Member nick being optional #2209
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
23 tasks
webtax-gh
approved these changes
Nov 6, 2020
Closed
vladfrangu
added a commit
to discordjs/discord-api-types
that referenced
this pull request
Dec 27, 2020
- Can be optional - ref: discord/discord-api-docs#2209
2 tasks
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.
This PR changes the
nickfield from being nullable to being nullable and optional.The documentation currently indicates that
nickin guild members is nullable but not optional, yet this field does not appear when receiving members without nicknames through the Gateway (e.g.GUILD_CREATE).