feat: Yandex sign-in with device code, keychain storage and account status
- ym-api wraps yamuse: device-code flow, token refresh, account status, and its own Error type that the UI acts on (expired, denied, network) - Credentials live in the system keychain, never print their tokens, and refresh when within a week of expiry; a rejected token is forgotten - Sign-in screen with code, QR, copy/open-in-browser, countdown and a pasted-token fallback; restoring/unreachable screens on startup - Sidebar account chip and Settings account card with Plus status and sign-out; Settings re-reads the account when opened - Live device-code test behind --ignored
This commit is contained in:
1 parent
c4928ae7fe
commit
43e8f86a5d
17 files changed
+2811
-127
No files matched your search
@@ -1,4 +1,11 @@
|
||||
//! Client for the unofficial Yandex Music API.
|
||||
//!
|
||||
//! Filled in by milestone 3 (sign-in) onwards; the app depends on this crate's
|
||||
//! own types only, never on whichever upstream wrapper it uses internally.
|
||||
//! Wraps [`yamuse`] so the app only ever sees this crate's own types: if the
|
||||
//! upstream wrapper changes or is swapped out, the UI doesn't move.
|
||||
|
||||
pub mod auth;
|
||||
mod client;
|
||||
mod error;
|
||||
|
||||
pub use client::{Account, YmClient};
|
||||
pub use error::{Error, Result};
|
||||
Reference in new issue
Block a user