All Versions
186
Latest Version
Avg Release Cycle
5 days
Latest Release
-

Changelog History
Page 3

  • v2.2.1 Changes

    • Versions:
      • Coroutines: 1.6.3 -> 1.6.4
      • MicroUtils: 0.11.12 -> 0.11.13
    • Core:
      • New typealiases for CommonMessage with all supported content types, more info: PR
    • Utils:
      • New extensions for all types of messages *.withContentOrNull and *.withContentOrThrow as analogies to the same ones from class casts
  • v2.2.0 Changes

    • Core:
      • For CopyMessage order of parameters has been changed
      • ReplyForce defaults changes:
      • All old companion properties (like ReplyForce.ReplyForceSelective) have been renamed:
        • ReplyForceSelective -> Selective
        • ReplyForceNonSelective -> NonSelective
        • ReplyForceDefault -> Default
      • New companion functions:
        • ReplyForce#Selective
        • ReplyForce#NonSelective
      • Rename CreatorChatMember -> OwnerChatMember
    • API:
      • For copyMessage order of parameters has been changed
    • Utils:
      • New extension Message#sameChat
      • New extension Message#sameMessage
      • New functions flatInlineKeyboard and flatReplyKeyboard
      • Experimentally add new triple of class casts: if*, *OrNull and *OrThrow
  • v2.1.3 Changes

    • Versions:
      • MicroUtils: 0.11.9 -> 0.11.12
    • Utils:
      • Rename UserId extension link to userLink
    • Core
      • ChatJoinRequest#inviteLink is nullable due to the fact that join requests without link do not require invite link
  • v2.1.2 Changes

    • Versions:
      • Coroutines: 1.6.1 -> 1.6.3
      • Ktor: 2.0.2 -> 2.0.3
      • MicroUtils: 0.11.6 -> 0.11.9
  • v2.1.1 Changes

    • API:
      • Now it is possible to edit any message text via editMessageText (but with warning)
      • Now it is possible to edit any message caption via editMessageCaption (but with warning)
      • Media message caption edit method (editMessageCaption) now returns the message with the same generic type (as it must be in telegram system)
      • New extensions TelegramBot#edit has been added for all possible editions types
      • New extensions TelegramBot#send has been added for all possible sending types
      • New extensions TelegramBot#delete has been added
    • Versions:
      • MicroUtils: 0.11.3 -> 0.11.6
  • v2.1.0 Changes

    ⚡️ This update contains including of Telegram Bot API 6.1

    • ➕ Add support of functionality for WebApps from Bot API 6.1
    • ➕ Add support of functionality for premium feature from Bot API 6.1
    • ➕ Add support of addedToAttachmentMenu in CommonUser from Bot API 6.1
    • ➕ Add support of secret_token in SetWebhook request from Bot API 6.1
    • ➕ Add support of createInvoiceLink request from Bot API 6.1
  • v2.0.3 Changes

    • Core:
      • New function regularln for simple creating of RegularTextSource with new line in the end
    • API:
      • New function downloadFileToTemp for simple downloading of file in filesystem and manipulation with avoiding of direct using input streams and other low-level things
    • Versions:
      • MicroUtils: 0.11.0 -> 0.11.3
  • v2.0.2 Changes

    • Versions:
      • MicroUtils: 0.10.8 -> 0.11.0
      • UUID: 0.4.0 -> 0.4.1
  • v2.0.1 Changes

    • Versions:
      • Ktor: 2.0.1 -> 2.0.2
      • MicroUtils: 0.10.5 -> 0.10.8
    • Utils:
      • TelegramBot#longPolling now accepts UpdatesFilter instead of FlowsUpdatesFilter
  • v2.0.0 Changes

    🚚 ALL PREVIOUS DEPRECATIONS HAVE BEEN REMOVED

    • 🏗 Behaviour Builder:
      • Mappers have been removed from waiters extensions
      • Triggers extensions now will use filtering inside of context receiver instead of passing the filters into BehaviourContext. That means that in the subcontext will not be used preinstalled filters for their BehaviourContext and filter of trigger will not be used in subcontext
      • Waiters do not take count parameter anymore
      • Waiters do not take filter parameter anymore. Use flows filters
    • Utils:
      • Add opportunity to get event messages with specific ChatEvent type using withEvent/requireWithEvent (by analog with withEvent and requireWithEvent)