@oxyhq/core 5.4.1 → 5.4.3

package/dist/esm/mixins/OxyServices.user.js

@@ -16,12 +16,23 @@ export function OxyServicesUserMixin(Base) {
             super(...args);
         }
         /**
-         * Get profile by username
-         */
-        async getProfileByUsername(username) {
+         * Get profile by username.
+         *
+         * @param username - The profile's username.
+         * @param options.cache - Defaults to `true` (5-minute TTL), matching prior
+         *   behavior. Pass `{ cache: false }` to force a registry-fresh read: the
+         *   request bypasses BOTH the cache lookup and the post-fetch cache write
+         *   (see {@link HttpService.request}'s `cache` handling), so it neither
+         *   serves nor overwrites any entry already cached for this key — a
+         *   previously cached response (if one exists) is left in place until its
+         *   own TTL expires or is explicitly invalidated elsewhere. Use this when a
+         *   caller must observe a just-written change (e.g. a privacy/consent flag)
+         *   that would otherwise be masked by the TTL window.
+         */
+        async getProfileByUsername(username, options) {
             try {
                 const user = await this.makeRequest('GET', `/profiles/username/${username}`, undefined, {
-                    cache: true,
+                    cache: options?.cache ?? true,
                     cacheTTL: 5 * 60 * 1000, // 5 minutes cache for profiles
                 });
                 return normalizeUserIdentity(user);
@@ -204,12 +215,23 @@ export function OxyServicesUserMixin(Base) {
             return users.map((user) => normalizeUserIdentity(user));
         }
         /**
-         * Get user by ID
-         */
-        async getUserById(userId) {
+         * Get user by ID.
+         *
+         * @param userId - The target user's id.
+         * @param options.cache - Defaults to `true` (5-minute TTL), matching prior
+         *   behavior. Pass `{ cache: false }` to force a registry-fresh read: the
+         *   request bypasses BOTH the cache lookup and the post-fetch cache write
+         *   (see {@link HttpService.request}'s `cache` handling), so it neither
+         *   serves nor overwrites any entry already cached for this key — a
+         *   previously cached response (if one exists) is left in place until its
+         *   own TTL expires or is explicitly invalidated elsewhere. Use this when a
+         *   caller must observe a just-written change (e.g. a privacy/consent flag)
+         *   that would otherwise be masked by the TTL window.
+         */
+        async getUserById(userId, options) {
             try {
                 const user = await this.makeRequest('GET', `/users/${userId}`, undefined, {
-                    cache: true,
+                    cache: options?.cache ?? true,
                     cacheTTL: 5 * 60 * 1000, // 5 minutes cache
                 });
                 return normalizeUserIdentity(user);