handy, but Telegram API's structure makes things a little complicated. 
                  
                  
                  For example there are 4 requests for different message modifications:
                  
                  
                  editMessageText
                  
                  
                  editMessageCaption
                  
                  
                  editMessageMedia
                  
                  
                  editMessageReplyMarkup
                  
                  
                  So users have to initiate a new request each time, like:
                  
                  
                  bot.EditMessageText()
                  
                  
                  bot.EditMessageCaption()
                  
                  
                  ...
                  
                  
                  
                  
                  
                  I was thinking to implement wrappers for related requests, in this case an EditMessage() struct will have EditText()
                  
                  
                  EditCaption()
                  
                  
                  ...
                  
                  
                  But I doubt this might complicate things, what do you think?
                  
                  
                
well you will offer a more functional version then, but that's more the same, basically you can do: object.method(3, 5) or you can do method(object, 3, 5)
this with templates will be better and easier
Обсуждают сегодня