(Gj,ndZddlmZddlZddlmZmZejdZdd Z dd Z ddZ ddZ dS)uHelpers for Telegram Bot API chat identifiers. Telegram's Bot API accepts a ``chat_id`` in two forms: a numeric ID (an int, e.g. ``123456789`` for a DM or ``-1001234567890`` for a channel/supergroup) or an ``@username`` string for public channels and groups. Hermes historically coerced every ``chat_id`` with ``int()``, which crashes on the username form (``ValueError: invalid literal for int()``). Normalizing here lets numeric IDs pass through as ints while usernames pass through unchanged — both are valid values for the Bot API. ) annotationsN)AnyUnionz@[A-Za-z0-9_]{4,32}chat_idrreturnUnion[int, str]ct|} t|S#ttf$r|cYSwxYw)a:Return a Bot API-compatible chat_id. Numeric values (incl. negative channel IDs) are returned as ``int``; any non-numeric value (e.g. an ``@username``) is returned as a stripped string. Telegram's Bot API accepts both, so this never raises on a username the way a bare ``int(chat_id)`` would. )strstripint TypeError ValueError)r chat_id_strs M/home/rurouni/.hermes/hermes-agent/plugins/platforms/telegram/telegram_ids.pynormalize_telegram_chat_idrsZg,,$$&&K; z "s2AAr c:tt|S)zBStable string key for a chat_id (for dict keys / persisted state).)r rrs rtelegram_chat_id_keyr&s )'22 3 33boolcttt|S)zHTrue when the value is an ``@username``-format Telegram chat identifier.)r_TELEGRAM_USERNAME_RE fullmatchr r rs rlooks_like_telegram_usernamer+s1 %//G 0B0B0D0DEE F FFr target_refUnion[str, None]cjt|}t|r|ndS)zCReturn the value when it is an ``@username`` target, else ``None``.N)r r r)rvalues rparse_telegram_username_targetr0s0  OO ! ! # #E077 A55TAr)rrrr)rrrr )rrrr)rrrr) __doc__ __future__rretypingrrcompilerrrrrrrr&s  #"""""  # #9::    4444 GGGG BBBBBBr