changes
This commit is contained in:
17
README.md
17
README.md
@@ -1,14 +1,13 @@
|
||||
# Telegram UserAuth UI
|
||||
|
||||
Reusable Angular-hosted UI for the Telegram login dialog.
|
||||
Reusable Angular-hosted UI for Telegram login.
|
||||
|
||||
The app now contains a single standalone page based on the extracted dialog design. It preserves the same visual states and the same state-switcher behavior from the provided HTML:
|
||||
The app now boots directly into the live `userauth` flow instead of a demo dialog. On load it:
|
||||
|
||||
- `ready`
|
||||
- `loading`
|
||||
- `checking`
|
||||
- `expired`
|
||||
- `error`
|
||||
- checks `GET /userauth/session`
|
||||
- creates a QR session with `POST /userauth/qr/create`
|
||||
- polls `GET /userauth/qr/poll?token=...` every 5 seconds
|
||||
- falls back to session re-check polling if QR creation or polling fails
|
||||
|
||||
## Run
|
||||
|
||||
@@ -51,9 +50,9 @@ Expected authenticated session payload:
|
||||
|
||||
Runtime expectations preserved by the UI:
|
||||
|
||||
- QR polling every 3 seconds
|
||||
- QR polling every 5 seconds
|
||||
- QR expiry after 100 checks on the frontend
|
||||
- direct Telegram login button support
|
||||
- direct Telegram open button using the same deep link returned by QR creation
|
||||
- fallback session re-check if QR creation fails
|
||||
|
||||
Cookie requirements expected by consumers:
|
||||
|
||||
Reference in New Issue
Block a user