[ 
https://issues.apache.org/jira/browse/CAMEL-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465019#comment-16465019
 ] 

ASF GitHub Bot commented on CAMEL-12478:
----------------------------------------

WillemJiang commented on a change in pull request #2318: CAMEL-12478: Allow use 
of custom keyboard
URL: https://github.com/apache/camel/pull/2318#discussion_r186275875
 
 

 ##########
 File path: 
components/camel-telegram/src/main/java/org/apache/camel/component/telegram/model/InlineKeyboardButton.java
 ##########
 @@ -0,0 +1,53 @@
+package org.apache.camel.component.telegram.model;
 
 Review comment:
   Please add the License header here.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> camel-telegram - Allow use of custom keyboard
> ---------------------------------------------
>
>                 Key: CAMEL-12478
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12478
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-telegram
>            Reporter: Willian Antunes
>            Priority: Major
>              Labels: features
>         Attachments: SNAG-0180.jpg
>
>
> The component as we have nowadays does not support configuration of custom 
> keyboard, it only makes use of the standard one.
> The method [sendMessage|https://core.telegram.org/bots/api#sendmessage] has 
> the field _reply_markup_ which allow the use of 
> [ReplyKeyboardMarkup|https://core.telegram.org/bots/api#replykeyboardmarkup] 
> to customize the standard keyboard.
> Acceptance Criteria:
>  * Send message with custom keyboard to interact with the bot using its 
> buttons.
>  * Disable custom keyboard when is required during chat conversation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to