Add message documentation #379
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
Closed
|
Awesome, thank you very much! I have created #380 for the remaining types. |
|
Let me kick Travis until the tests pass again. The tests hit the live Telegram API so it often runs into rate limiting issues... |
|
Alright it looks like one of the tests actually are failing, but not because of this PR. I'll merge it in even though Travis is complaining. Edit: being fixed in #381 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Close #240
I've added Message documentation from API to godoc. Not rocket science, but costed me about an hour to copy-paste and fit formatting, spelling, type references, etc.
P.S.: I think I can do that for other API types, if that would be the case, please create an issue and assign it to me.