@aastrika/ai-elements 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -6,6 +6,26 @@ see at a glance what to expect when they upgrade.
 Versions follow semver: a **minor** adds something, a **patch** fixes something,
 and neither removes anything a host was using.
 
+## 0.6.1
+
+**Fixed**
+- The usage report showed one person's figures instead of the whole
+  organisation's — and nothing at all when the signed-in name did not match the
+  name recorded on their content. Every request body was given the signed-in
+  `creator`, including the report, where that field means "filter to this
+  person" rather than "this is who I am". The report is no longer given one; the
+  dashboard's own picker still filters as before
+
+**Added**
+- `creatorName` in `configure()` — the signed-in person's display name, shown in
+  the report while `creator` stays what it groups by. A host can now use a
+  stable handle as `creator` and let people rename themselves without splitting
+  their history across two creators. Optional: omit it and the report shows
+  `creator`, exactly as today
+
+Needs the service to be on a build that stores `creator_name`; on an older one
+the field is ignored and nothing changes.
+
 ## 0.6.0
 
 Adds behaviour rather than API: the tags, attributes and events are exactly

package/aastrika-elements.d.ts

@@ -43,8 +43,20 @@ export interface AastrikaConfig {
   apiBase: string;
   /** Headers proving the caller may use the service. Called before every request. */
   getAuthHeaders?: () => Record<string, string> | Promise<Record<string, string>>;
-  /** The username signed into YOUR application. Attribution, never verified. */
+  /**
+   * A STABLE key for whoever is signed into YOUR application — a login handle
+   * or an id, never a display name. The usage report groups and filters by it,
+   * so renaming somebody must not change it. Attribution, never verified.
+   */
   creator?: () => string | null;
+  /**
+   * The same person's display name, e.g. "Prince Gupta". Shown in the usage
+   * report; `creator` remains what it groups by, so people can rename
+   * themselves without splitting their history. Optional — omit it and the
+   * report shows `creator`, so send one whenever `creator` is an opaque id,
+   * or the report fills with UUIDs.
+   */
+  creatorName?: () => string | null;
   /** Called whenever a request fails, so your monitoring hears about it. */
   onError?: (error: AastrikaError) => void;
 }