@oxyhq/core 21.1.0 → 21.2.0

package/dist/types/mixins/OxyServices.accounts.d.ts

@@ -180,6 +180,21 @@ export interface CreateAccountInput {
     };
     bio?: string;
     avatar?: string;
+    /**
+     * Named color preset KEY — `'blue'`, `'mint'`, … — never a hex value. The
+     * account graph's half of `User.color`, which every account DTO already
+     * carries; this is how one gets WRITTEN for an account you administer.
+     *
+     * Set it HERE rather than after the fact. For a managed account the colour is
+     * a visual identity, and an account that is discoverable without one and
+     * acquires it on a second request is a face that changes by itself.
+     *
+     * Omitted is not "no colour": the platform assigns a random preset, exactly as
+     * it did before this field existed. A reserved preset is refused unless the
+     * account has a claim to it — the administrator's own entitlements are not the
+     * ones weighed.
+     */
+    color?: string;
     /**
      * What the account is about. ORDERED — the FIRST element is the primary
      * category, so a picker must submit them in the order the user arranged them
@@ -224,6 +239,15 @@ export interface UpdateAccountInput {
     };
     bio?: string | null;
     avatar?: string | null;
+    /**
+     * Named color preset KEY, same vocabulary as `CreateAccountInput['color']`.
+     *
+     * NOT nullable, unlike `bio` and `avatar`: the column is `NOT NULL` with a
+     * default, so an account always HAS a colour and there is no "clear" to
+     * express. Sending the value the account already carries is always accepted,
+     * so a client may PATCH back the object it was served.
+     */
+    color?: string;
     /**
      * Replaces the WHOLE list, in the order given — there is no add/remove verb,
      * because a partial edit cannot express a re-ordering and the order is what

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oxyhq/core",
-  "version": "21.1.0",
+  "version": "21.2.0",
   "description": "OxyHQ SDK Foundation — API client, authentication, cryptographic identity, and shared utilities",
   "main": "dist/cjs/index.js",
   "module": "dist/esm/index.js",
@@ -116,7 +116,7 @@
   "dependencies": {
     "@noble/ciphers": "^1.3.0",
     "@noble/hashes": "^1.8.0",
-    "@oxyhq/contracts": "^0.31.0",
+    "@oxyhq/contracts": "^0.32.0",
     "@oxyhq/protocol": "^0.2.0",
     "@scure/bip39": "^1.6.0",
     "@types/elliptic": "^6.4.18",

package/src/mixins/OxyServices.accounts.ts

@@ -201,6 +201,21 @@ export interface CreateAccountInput {
   name?: { first?: string; last?: string; displayName?: string };
   bio?: string;
   avatar?: string;
+  /**
+   * Named color preset KEY — `'blue'`, `'mint'`, … — never a hex value. The
+   * account graph's half of `User.color`, which every account DTO already
+   * carries; this is how one gets WRITTEN for an account you administer.
+   *
+   * Set it HERE rather than after the fact. For a managed account the colour is
+   * a visual identity, and an account that is discoverable without one and
+   * acquires it on a second request is a face that changes by itself.
+   *
+   * Omitted is not "no colour": the platform assigns a random preset, exactly as
+   * it did before this field existed. A reserved preset is refused unless the
+   * account has a claim to it — the administrator's own entitlements are not the
+   * ones weighed.
+   */
+  color?: string;
   /**
    * What the account is about. ORDERED — the FIRST element is the primary
    * category, so a picker must submit them in the order the user arranged them
@@ -242,6 +257,15 @@ export interface UpdateAccountInput {
   name?: { first?: string; last?: string; displayName?: string };
   bio?: string | null;
   avatar?: string | null;
+  /**
+   * Named color preset KEY, same vocabulary as `CreateAccountInput['color']`.
+   *
+   * NOT nullable, unlike `bio` and `avatar`: the column is `NOT NULL` with a
+   * default, so an account always HAS a colour and there is no "clear" to
+   * express. Sending the value the account already carries is always accepted,
+   * so a client may PATCH back the object it was served.
+   */
+  color?: string;
   /**
    * Replaces the WHOLE list, in the order given — there is no add/remove verb,
    * because a partial edit cannot express a re-ordering and the order is what

package/src/mixins/__tests__/accounts.test.ts

@@ -255,13 +255,20 @@ describe('OxyServices.accounts', () => {
     it('posts the payload, unwraps `account`, and busts every list', async () => {
       makeRequestSpy.mockResolvedValue({ account: accountNodeFixture });
 
-      const result = await oxy.createAccount({ kind: 'organization', username: 'oxy-org' });
+      const result = await oxy.createAccount({
+        kind: 'organization',
+        username: 'oxy-org',
+        color: 'purple',
+      });
 
       expect(result).toEqual(accountNodeFixture);
+      // `color` rides the CREATE body, not a follow-up patch: an account that is
+      // discoverable without its colour and acquires one on a second request is
+      // a face that changes by itself.
       expect(makeRequestSpy).toHaveBeenCalledWith(
         'POST',
         '/accounts',
-        { kind: 'organization', username: 'oxy-org' },
+        { kind: 'organization', username: 'oxy-org', color: 'purple' },
         expect.objectContaining({ cache: false }),
       );
       expect(clearEntrySpy).toHaveBeenCalledWith('GET:/accounts');
@@ -273,13 +280,13 @@ describe('OxyServices.accounts', () => {
     it('patches, unwraps `account`, and busts the detail + lists', async () => {
       makeRequestSpy.mockResolvedValue({ account: accountNodeFixture });
 
-      const result = await oxy.updateAccount('acc1', { bio: 'hello' });
+      const result = await oxy.updateAccount('acc1', { bio: 'hello', color: 'mint' });
 
       expect(result).toEqual(accountNodeFixture);
       expect(makeRequestSpy).toHaveBeenCalledWith(
         'PATCH',
         '/accounts/acc1',
-        { bio: 'hello' },
+        { bio: 'hello', color: 'mint' },
         expect.objectContaining({ cache: false }),
       );
       expect(clearEntrySpy).toHaveBeenCalledWith('GET:/accounts/acc1');