@chaosity/location-client-react 0.3.0 → 0.3.1

package/dist/provider/LocationClientProvider.d.ts

@@ -1,4 +1,5 @@
 import type { ClientConfig } from '@chaosity/location-client';
+import { type AppConfigClaims } from '@chaosity/location-client';
 import type { ReactNode } from 'react';
 /**
  * Per-request transport options.
@@ -26,6 +27,24 @@ export interface LocationClient {
         serviceId: string;
     };
     send<TInput, TOutput>(command: TInput, options?: SendOptions): Promise<TOutput>;
+    /**
+     * This application's own configuration, read from the access token —
+     * bias precision, and the countries it is scoped to (api#65).
+     *
+     * Here so a React app can SHOW its own settings: populate a country
+     * selector with the markets it serves, label a settings screen. Being a
+     * few minutes stale is cosmetic for that.
+     *
+     * It is not an entitlement check, and the `countries` value must not be
+     * used to shape requests. The token is a snapshot; the API reads the scope
+     * fresh from the application row on every call. Injecting a stale scope
+     * turns a request that would have succeeded into a 400. See
+     * `AppConfigClaims` in @chaosity/location-client for the measurement.
+     *
+     * Returns `{}` when the token carries no application config, which is the
+     * case until one is set in the portal.
+     */
+    getAppConfig(): AppConfigClaims;
 }
 interface LocationClientContextValue {
     client: LocationClient | null;

package/dist/provider/LocationClientProvider.js

@@ -170,6 +170,13 @@ export function LocationClientProvider({ children, getConfig, }) {
                     await ensureValidTokenRef.current();
                     return baseClient.send(command, options);
                 },
+                // Reads whatever token the client currently holds. Deliberately not
+                // awaiting a refresh: this is display data, callers expect it to be
+                // synchronous, and a token that is minutes from expiry carries the
+                // same application config as its replacement will.
+                getAppConfig() {
+                    return baseClient.getAppConfig();
+                },
             };
             setClient(refreshing);
             scheduleRefreshRef.current();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chaosity/location-client-react",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "React bindings for Chaosity Location Service client",
   "type": "module",
   "main": "dist/index.js",
@@ -34,7 +34,7 @@
     "url": "https://github.com/chaosity-io/location-service-client-react/issues"
   },
   "dependencies": {
-    "@chaosity/location-client": "^0.2.1",
+    "@chaosity/location-client": "^0.3.0",
     "debug": "^4.4.3"
   },
   "peerDependencies": {