Releases: RAprogramm/telegram-webapp-sdk
Releases · RAprogramm/telegram-webapp-sdk
v0.3.1
v0.3.0
v0.2.18
v0.2.17
v0.2.16
Fixed
- Made
use_telegram_contextYew hook reactive to properly handle cases when
the Telegram SDK initializes after component mount. The hook now uses
requestAnimationFrameto efficiently poll for context availability and
automatically updates when the context becomes ready (#141, #142)
Full Changelog: v0.2.15...v0.2.16
v0.2.15
Fixed
- Restored compatibility with the latest nightly toolchains by probing support
fordoc_cfganddoc_auto_cfg, ensuring docs.rs builds succeed after the
upstream removal ofdoc_auto_cfg.
Changed
- Emitted explicit
cargo:rustc-check-cfgdeclarations for both documentation
capability flags so that future compilers surface helpful diagnostics when
the build script conditions fall out of sync.
v0.2.14
Fixed
- Guarded the nightly-only
doc_auto_cfgattribute behind a compiler channel
probe so documentation builds on docs.rs no longer fail on stable toolchains.
Changed
- Added a lightweight build-time check using
version_checkto conditionally
enable nightly-only documentation features without impacting stable
consumers.
v0.2.13
Changed
- Upgraded to
masterror0.24 across the workspace, ensuring the SDK and demo
benefit from the latest error handling improvements.
v0.2.10
Added
- Propagated
query_idfrominitDataintoTelegramInitDataand exposed it
through the global context, including a wasm integration test that verifies
the parsed value.
Changed
- Extended the mock environment and documentation to surface the optional
query_idparameter, ensuring examples highlight how to handle inline query
responses.
v0.2.9
Fixed
- Corrected launch parameter parsing to honor the first query entry,
percent-decode values (includingtgWebAppPlatform), and preserve
boolean flags.
Added
- Regression tests covering decoded query parameters for
get_launch_params.