GitHub user Neffez opened a pull request:
https://github.com/apache/camel/pull/1413
Camel-Telegram: Support for type "Document"
The telegram type "Document" is a general file (as opposed to photos,
videos or audio files) and can be in any format. A Document can also be one of
the already supported types, but then it's uncompressed (e.g. photos).
The benefits of using the Document type are:
- Receiving and sending uncompressed files
- Receiving and sending files of any format
This pull request contains the support for incoming and outgoing documents
and unit tests.
Also see: https://core.telegram.org/bots/api#document
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Neffez/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1413.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1413
----
commit 84ccaa1fd64da1616ab1d1def2e6df7d70d63fa2
Author: Steffen Eitelmann <[email protected]>
Date: 2017-01-20T12:15:20Z
added support of telegram documents (general files, uncompressed)
commit 7f651509c2d140d2794182eeab4420d619d84344
Author: Steffen Eitelmann <[email protected]>
Date: 2017-01-20T12:27:54Z
fix copy paste error
commit 33a901ce16dd18be6af8cb7dcf0f6bd63e3fb897
Author: Neffez <[email protected]>
Date: 2017-01-20T12:52:33Z
no extension for general file
commit e033b822268f1e8896fc058bd6023c883191c39e
Author: Neffez <[email protected]>
Date: 2017-01-20T12:53:06Z
added unit tests for outgoing and incoming documents
commit 6dea3fbe847e5a4ba2787421e35e46f23e301457
Author: Neffez <[email protected]>
Date: 2017-01-20T12:56:41Z
added further unit tests for outgoing and incoming documents
commit 91194bb1bbdb978878037c0b1019db147d61bbe9
Author: Neffez <[email protected]>
Date: 2017-01-20T13:01:51Z
manage imports
commit 01d9633870ef17a8a8f2e4b8ba990faeb5562977
Author: Neffez <[email protected]>
Date: 2017-01-20T13:04:37Z
updated documentation (added type OutgoingDocumentMessage)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
