@idosgames/core 0.1.2 → 0.1.4

package/dist/index.d.cts

@@ -2960,10 +2960,28 @@ declare class AuthenticationService {
     private readonly ctx;
     private authContext;
     private refreshing;
+    private rememberSession;
+    private sessionAuthType;
+    private sessionEmail;
+    private sessionPassword;
     constructor(ctx: ClientContext);
     get context(): AuthContext | null;
     get isLoggedIn(): boolean;
+    /** The PERSISTED login method — what a cold start would replay. `None` = nothing to replay. */
     get lastAuthType(): AuthType;
+    /**
+     * "Remember me" — call BEFORE a login method (it is read when the login completes).
+     *
+     * On (the default, and the behaviour of every release before this one) a successful login is
+     * written to storage, so the next launch signs the player back in silently. Off, nothing is
+     * written and the next launch opens on the login screen — and any previously remembered session
+     * is dropped, so a player who unticks the box on a shared machine is not left behind on disk.
+     *
+     * Off does NOT weaken the current session: the credentials stay in memory for this tab, so the
+     * transport's automatic 401 re-login still works.
+     */
+    setRememberSession(remember: boolean): void;
+    get remembersSession(): boolean;
     private baseRequest;
     loginWithDeviceID(): Promise<OperationResult<ClientState>>;
     loginWithTelegram(): Promise<OperationResult<ClientState>>;
@@ -2997,11 +3015,28 @@ declare class AuthenticationService {
      * login method themselves in that case.
      */
     autoLogin(): Promise<OperationResult<ClientState>>;
-    /** Registered with the transport: a 401 transparently triggers one re-login + retry. */
+    private replay;
+    /**
+     * Registered with the transport: a 401 transparently triggers one re-login + retry.
+     *
+     * Reads the SESSION tier first so a player who declined "remember me" still recovers from an
+     * expired ticket; it falls back to the persisted tier for a client that has not logged in yet
+     * this tab (a 401 on the very first call after a cold start).
+     */
     refreshSession(): Promise<string | null>;
+    /**
+     * Ends the session and forgets it on both tiers.
+     *
+     * Clearing storage is deliberate: without it a logout did not survive a reload — the next launch
+     * replayed the very account the player had just left, which on a shared machine is the one moment
+     * it must not do that. To sign out but stay remembered, do not call this.
+     */
     logout(): void;
     static isValidEmail(email: string): boolean;
     static isValidPasswordLength(password: string): boolean;
+    /** Email/password go to the session tier always, to storage only when remembering. */
+    private keepEmailCredentials;
+    private forgetSession;
     private applyAuthContext;
     private fetchAndApplyClientState;
 }

package/dist/index.d.ts

@@ -2960,10 +2960,28 @@ declare class AuthenticationService {
     private readonly ctx;
     private authContext;
     private refreshing;
+    private rememberSession;
+    private sessionAuthType;
+    private sessionEmail;
+    private sessionPassword;
     constructor(ctx: ClientContext);
     get context(): AuthContext | null;
     get isLoggedIn(): boolean;
+    /** The PERSISTED login method — what a cold start would replay. `None` = nothing to replay. */
     get lastAuthType(): AuthType;
+    /**
+     * "Remember me" — call BEFORE a login method (it is read when the login completes).
+     *
+     * On (the default, and the behaviour of every release before this one) a successful login is
+     * written to storage, so the next launch signs the player back in silently. Off, nothing is
+     * written and the next launch opens on the login screen — and any previously remembered session
+     * is dropped, so a player who unticks the box on a shared machine is not left behind on disk.
+     *
+     * Off does NOT weaken the current session: the credentials stay in memory for this tab, so the
+     * transport's automatic 401 re-login still works.
+     */
+    setRememberSession(remember: boolean): void;
+    get remembersSession(): boolean;
     private baseRequest;
     loginWithDeviceID(): Promise<OperationResult<ClientState>>;
     loginWithTelegram(): Promise<OperationResult<ClientState>>;
@@ -2997,11 +3015,28 @@ declare class AuthenticationService {
      * login method themselves in that case.
      */
     autoLogin(): Promise<OperationResult<ClientState>>;
-    /** Registered with the transport: a 401 transparently triggers one re-login + retry. */
+    private replay;
+    /**
+     * Registered with the transport: a 401 transparently triggers one re-login + retry.
+     *
+     * Reads the SESSION tier first so a player who declined "remember me" still recovers from an
+     * expired ticket; it falls back to the persisted tier for a client that has not logged in yet
+     * this tab (a 401 on the very first call after a cold start).
+     */
     refreshSession(): Promise<string | null>;
+    /**
+     * Ends the session and forgets it on both tiers.
+     *
+     * Clearing storage is deliberate: without it a logout did not survive a reload — the next launch
+     * replayed the very account the player had just left, which on a shared machine is the one moment
+     * it must not do that. To sign out but stay remembered, do not call this.
+     */
     logout(): void;
     static isValidEmail(email: string): boolean;
     static isValidPasswordLength(password: string): boolean;
+    /** Email/password go to the session tier always, to storage only when remembering. */
+    private keepEmailCredentials;
+    private forgetSession;
     private applyAuthContext;
     private fetchAndApplyClientState;
 }