Skip to content

Fetching telegram username #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fetching telegram username #5

wants to merge 3 commits into from

Conversation

@karthu0301
Copy link

@karthu0301 karthu0301 commented Apr 15, 2025

  • Implemented fallback UI in QueueActions when Telegram user data is not injected
  • Modified TelegramWebApp to always render main components (QueueDisplay, QueueActions, QueueAdmin), even when user context is missing
  • Removed blocking error message that previously prevented rendering if Telegram WebApp SDK or initData was unavailable
  • Ensured safe handling of userIdentifier in QueueActions using either Telegram username, ID, or manual fallback
  • Added debug logging to help verify Telegram SDK injection state

TODO:

  • Confirm if Telegram eventually injects user context after domain propagation
  • Replace fallback name prompt once Telegram user info is reliably injected
  • Clean up debug logging before final deployment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@karthu0301