Bot API 3.1 #551
Merged
Bot API 3.1 #551
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
jacklul
approved these changes
Jul 9, 2017
Keep track of methods that need a dummy parameter for some cURL versions to function properly.
Make Request::encodeFile public, as it's needed to send files, letting users make use of it.
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 adds all new features from the Bot API 3.1 update.
Refactor
Requestclass, removing most custom method implementations.Note: New fields for
Chatentity have NOT been added to the database structure, as the data can be unreliable, due to only being returned when explicitly requesting it viagetChat.