fix(Invite): #guild never resolving into a Guild #6742
Merged
Conversation
This file contains 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
SpaceEEC
requested changes
Oct 2, 2021
Co-authored-by: SpaceEEC <spaceeec@yahoo.com>
SpaceEEC
approved these changes
Oct 2, 2021
iCrawl
approved these changes
Oct 2, 2021
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.
Please describe the changes this PR makes and why it should be merged:
This PR fixed a bug with Invite#guild where it was documented as possibly being InviteGuild or Guild but it could never be the latter since
data.guildcan never be an instanceof Guild, since that's the raw data received from Discord. This shouldn't be breaking as the docs and types already had this behavior predicted, it was just poorly implementedStatus and versioning classification: