richButtonStyle
richButtonStyle
Section titled “richButtonStyle”No description provided by the pinned schema.
Signature
Section titled “Signature”richButtonStyle#03c610bd flags:# bg_primary:flags.0?true bg_danger:flags.1?true bg_success:flags.2?true link:flags.3?true = RichButtonStyle;Result type
Section titled “Result type”RichButtonStyle
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| bg_primary | flags.0?true | flags.0 | — | No description provided by the pinned schema. |
| bg_danger | flags.1?true | flags.1 | — | No description provided by the pinned schema. |
| bg_success | flags.2?true | flags.2 | — | No description provided by the pinned schema. |
| link | flags.3?true | flags.3 | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| bg_primary | 0 | Controlled by flags; present when this bit is set. |
| bg_danger | 1 | Controlled by flags; present when this bit is set. |
| bg_success | 2 | Controlled by flags; present when this bit is set. |
| link | 3 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.types import RichButtonStylePublic access: miniproto.raw.types.RichButtonStyle.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.types import RichButtonStyle
# Naming the raw constructor class is local only; it performs no I/O or network request.constructor_type = RichButtonStyleResult family
Section titled “Result family”Relationships
Section titled “Relationships”- Result family:
RichButtonStyle - Accepted by:
pageButton,textButton
Provenance
Section titled “Provenance”- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 229 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=78; core_only_count=18; overlap_count=2285; tdlib_only_count=195
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2470; tdesktop_only=null; tdlib_only=accessPointRule, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret