Fix deserialization of nullable field "premium_type" #210
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
sll552
added a commit
to sll552/DiscordBee
that referenced
this pull request
Oct 8, 2022
sll552
added a commit
to sll552/DiscordBee
that referenced
this pull request
Oct 8, 2022
sll552
added a commit
to sll552/DiscordBee
that referenced
this pull request
Oct 8, 2022
|
Thank you for your contribution. This is now released in |
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.
I came across this issue because of increasing reports of users that their presence is not showing up lately. I guess the Discord API now actually omits the
premium_typefield at least if the user is not subscribed.In VS i could not find any reference to this member of the User class, is it even used or could it be removed entirely?