Conversation
Member
|
Suggestion: Eventually we could have a ChatType class, listing off all the types, as we do in ChatAction. |
Member
Author
|
@leandrotoledo I thought about that, but at the time of implementation, there was no use for that. There was no situation where you would assign the chat type, you'd only decode from json |
This was referenced Jan 9, 2018
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The class
GroupChathas been refactored toChatand now represents all chats. Also,Messagenow contains the optional fieldssupergroup_chat_created,migrate_to_chat_id,migrate_from_chat_idandchannel_chat_created.