fix: nilable input_message_content for inline voice results

Fixes hangyas#16
vladfaust · Jun 28, 2017 · fab503d · fab503d
1 parent 64f77b5
commit fab503d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/telegram_bot/types/inline/inline_query_result_cached_voice.cr b/src/telegram_bot/types/inline/inline_query_result_cached_voice.cr
@@ -8,7 +8,7 @@ module TelegramBot
       voice_file_id:         String,
       title:                 String,
       reply_markup:          {type: InlineKeyboardMarkup, nilable: true},
-      input_message_content: InputMessageContent,
+      input_message_content: {type: InputMessageContent, nilable: true},
     }
 
     JSON.mapping({{FIELDS}})

diff --git a/src/telegram_bot/types/inline/inline_query_result_voice.cr b/src/telegram_bot/types/inline/inline_query_result_voice.cr
@@ -9,7 +9,7 @@ module TelegramBot
       title:                 String,
       voice_duration:        {type: Int32, nilable: true},
       reply_markup:          {type: InlineKeyboardMarkup, nilable: true},
-      input_message_content: InputMessageContent,
+      input_message_content: {type: InputMessageContent, nilable: true},
     }
 
     JSON.mapping({{FIELDS}})