@molecule/app-react-native 1.0.4 → 2.0.0

package/README.md

@@ -3,7 +3,7 @@ AUTO-GENERATED — DO NOT EDIT THIS FILE.
 Generated by `mlcl sync-docs` from the package's src/index.ts JSDoc + mlcl/registry.json.
 Edits here are overwritten on the next commit (molecule's pre-commit hook regenerates).
 To change this document, edit the module-level JSDoc in src/index.ts.
-Generated: 2026-10-23T14:59:33.332Z
+Generated: 2026-10-25T20:03:36.978Z
 -->
 
 # @molecule/app-react-native
@@ -208,9 +208,12 @@ interface AuthClient<T = UserProfile, TRegister extends RegisterExtraShape<TRegi
     confirmPasswordReset(data: PasswordResetConfirm): Promise<void>;
     /**
      * Updates the current user's profile.
-     * Returns the saved response. If the session is explicitly replaced or ended
-     * while the request is pending, that response does not replace the current
-     * session's user or persisted cache.
+     * Returns the saved profile: the answer applied onto the signed-in user field
+     * by field, with or without an `id` — a field it carries replaces the value
+     * (`null` clears it), one it omits or leaves `undefined` is kept, so a field
+     * cleared by omission must arrive as `null`. A non-object answer is returned
+     * as it came. An answer for a replaced or ended session leaves the current one
+     * untouched.
      */
     updateProfile(data: Partial<T>): Promise<T>;
     /**
@@ -266,9 +269,6 @@ interface AuthClient<T = UserProfile, TRegister extends RegisterExtraShape<TRegi
      * Resolves when the session restore started by `initialize()` has settled — the point
      * after which the client knows whether this visitor is signed in.
      *
-     * Resolves IMMEDIATELY when no restore is in flight: before `initialize()` is ever
-     * called, and after it has finished. A restore that failed resolves too (it settled the
-     * question), so an HTTP client can await this before every request without risking one
 // … truncated — the full declaration is in node_modules/@molecule/app-react-native/dist
 ```
 
@@ -476,12 +476,50 @@ interface HttpClient {
   addErrorInterceptor(interceptor: ErrorInterceptor): () => void
   /**
    * Sets the authorization token.
+   *
+   * A static token: every request carries it until the next `setAuthToken` call. A client
+   * that has a {@link HttpClient.setAuthTokenResolver | resolver} (registered through
+   * `@molecule/app-http`'s `setAuthTokenSource`) ignores this value when it assembles a
+   * request — the resolver IS the session, and reading it per request is what keeps a
+   * session adopted without an auth event from sending the previous account's bearer. Once
+   * the resolver is removed, the static token is sent again.
    */
   setAuthToken(token: string | null): void
   /**
-   * Returns the current authorization token, or `null` if not set.
+   * Returns the token the client applies to its next request: the resolver's answer when one
+   * is registered, else the static token from `setAuthToken`.
    */
   getAuthToken(): string | null
+  /**
+   * Registers the LIVE token resolver every request of this client reads, or clears it with
+   * `null`.
+   *
+   * `@molecule/app-http`'s `setAuthTokenSource()` calls this on every client it bonds, and the
+   * client MUST consult the resolver again each time it assembles a request (and report it from
+   * `getAuthToken()`). A session can change with no auth event and no observable state change —
+   * `authClient.setSession()` with the same profile data, or the OAuth callback's
+   * `setAccessToken()` — so a token pushed only at bond time or on `login`/`logout` events
+   * leaves every later request carrying the PREVIOUS session's bearer while the UI shows the
+   * new one.
+   *
+   * The resolved token takes the static token's place, with the same precedence: an
+   * `Authorization` header passed per request or in the client's default headers wins over it
+   * exactly where it won over a static token in this transport.
+   *
+   * A resolver that returns `null` (or `undefined`) means "this session has no body token": the
+   * request carries no `Authorization` header of the client's own. A cookie-session API issues
+   * no bearer, and the server prefers the header over the fresh cookie, so a kept bearer
+   * authenticates as the prior — possibly deleted — session.
+   *
+   * Optional, so an implementation written against the previous interface still conforms.
+   * `setAuthTokenSource()` follows such a client through a request interceptor instead, pushing
+   * the source with `setAuthToken` before each request: that request carries the change only
+   * when the transport applies its token after running its interceptors, so a transport that
+   * applies it earlier sends a session adopted mid-page from the following request on.
+   *
+   * @param resolver - Returns the current access token (or null/undefined), or `null` to clear.
+   */
+  setAuthTokenResolver?(resolver: AuthTokenResolver | null): void
   /**
    * Registers a handler for authentication errors (401).
    *
@@ -1405,7 +1443,7 @@ interface UseAuthResult<
    *
    * `setUser` alone does NOT sign the client in, and `setAccessToken` changes
    * storage only — using those two for a caller-issued session leaves every
-   * `authenticated` read signed out (xr-molecule-flash-m178).
+   * `authenticated` read signed out.
    */
   setSession: AuthClient<T>['setSession']
   isAuthenticated: boolean
@@ -1806,6 +1844,34 @@ How far the return-page verification has got.
 type VerifyPaymentReturnStatus = 'idle' | 'verifying' | 'verified' | 'failed'
 ```
 
+#### `UseTShorthandOptions`
+
+Options for the shorthand form of {@link UseTFunction}: the fallback text is
+passed positionally, so only `count` remains here.
+
+```typescript
+type UseTShorthandOptions = Omit<TranslateOptions, 'defaultValue'>
+```
+
+#### `UseTFunction`
+
+Translation function returned by `useT()`.
+
+Two compatible call forms:
+
+- `t(key, values?, options?)` — the {@link I18nProvider.t} signature.
+- `t(key, fallback, options?)` — a string second argument is the inline
+  English `defaultValue`, with optional `count` for pluralization.
+
+Its identity is stable while the i18n provider instance is unchanged, so it
+can be used directly as an effect dependency.
+
+```typescript
+type UseTFunction = I18nProvider['t'] & {
+  (key: string, fallback: string, options?: UseTShorthandOptions): string
+}
+```
+
 ### Functions
 
 #### `useAppState()`
@@ -2665,15 +2731,32 @@ function useTranslation(): UseTranslationResult
 
 Hook to get just the translation function.
 
+The returned function keeps ONE identity for as long as the provider
+instance is unchanged, so it is safe as an effect dependency: an effect
+written as `useEffect(..., [t])` does not re-run on ordinary re-renders or on
+a locale change. The hook still re-renders the calling component on every
+locale notification (including `addTranslations` for the active locale), so
+text it reads while rendering is current. A value memoized on `[t]` alone
+keeps the old text after a locale switch: `useMemo(() => t(...), [t])`, or a
+`React.memo` child that receives `t` as a prop. Call `useT()` inside that
+child, or add `useLocale()` to the dependencies.
+
+Call it in either of two compatible forms:
+
+- `t(key, values?, options?)` — the provider signature from
+  `@molecule/app-i18n`, e.g. `t('cart.total', { total })`.
+- `t(key, fallback, options?)` — a shorthand for the common inline-English
+  call: a string second argument is the `defaultValue`, so
+  `t('cart.empty', 'Your cart is empty')` equals
+  `t('cart.empty', undefined, { defaultValue: 'Your cart is empty' })`.
+  Interpolation and pluralization still work:
+  `t('cart.items', '{{count}} items', { count: 3 })`.
+
 ```typescript
-function useT(): (
-  key: string,
-  values?: InterpolationValues,
-  options?: { defaultValue?: string; count?: number },
-) => string
+function useT(): UseTFunction
 ```
 
-**Returns:** The translation function
+**Returns:** The translation function (stable identity while the provider is unchanged).
 
 #### `useLocale()`
 
@@ -3148,7 +3231,7 @@ Peer dependencies:
 
 - `@molecule/app-keyboard` ^1.0.1
 - `@molecule/app-lifecycle` ^1.0.1
-- `@molecule/app-react` ^1.0.1
+- `@molecule/app-react` ^2.0.0
 - `react` ^18.0.0 || ^19.0.0
 - `react-native` >=0.72.0
 - `react-native-safe-area-context` >=4.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@molecule/app-react-native",
-  "version": "1.0.4",
+  "version": "2.0.0",
   "description": "React Native framework bindings for molecule.dev",
   "homepage": "https://www.molecule.dev/packages/app-react-native",
   "type": "module",
@@ -33,7 +33,7 @@
     "directory": "packages/app/frameworks/react-native"
   },
   "devDependencies": {
-    "@molecule/app-react": "1.10.1",
+    "@molecule/app-react": "2.0.0",
     "@types/node": "26.6.5",
     "react": "19.3.1",
     "typescript": "6.0.3",
@@ -42,7 +42,7 @@
   "peerDependencies": {
     "@molecule/app-keyboard": "^1.0.1",
     "@molecule/app-lifecycle": "^1.0.1",
-    "@molecule/app-react": "^1.0.1",
+    "@molecule/app-react": "^2.0.0",
     "react": "^18.0.0 || ^19.0.0",
     "react-native": ">=0.72.0",
     "react-native-safe-area-context": ">=4.0.0"