`gj,pdZddlmZddlZddlmZmZejdZd dZ d dZ d dZ d d Z y)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}czt|j} 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)chat_id chat_id_strs Z/root/.hermes/venv/lib/python3.12/site-packages/plugins/platforms/telegram/telegram_ids.pynormalize_telegram_chat_idrs@g,$$&K; z "s &::c*tt|S)zBStable string key for a chat_id (for dict keys / persisted state).)rrr s rtelegram_chat_id_keyr&s )'2 33clttjt|j S)zHTrue when the value is an ``@username``-format Telegram chat identifier.)bool_TELEGRAM_USERNAME_RE fullmatchrrrs rlooks_like_telegram_usernamer+s& %//G 0B0B0DE FFrcRt|j}t|r|SdS)zCReturn the value when it is an ``@username`` target, else ``None``.N)rrr) target_refvalues rparse_telegram_username_targetr0s&  O ! ! #E075ATAr)r rreturnzUnion[int, str])r rrr)r rrr)rrrzUnion[str, None]) __doc__ __future__rretypingrrcompilerrrrrrrr$s? #  # #9: 4 G Br