@amityco/ts-sdk-react-native 7.27.1-65962e20.0 → 7.27.1-d6964077.0

package/dist/channelRepository/api/createChannel.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"createChannel.d.ts","sourceRoot":"","sources":["../../../src/channelRepository/api/createChannel.ts"],"names":[],"mappings":"AAUA;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,aAAa;;;;;;yIAwCzB,CAAC"}
+{"version":3,"file":"createChannel.d.ts","sourceRoot":"","sources":["../../../src/channelRepository/api/createChannel.ts"],"names":[],"mappings":"AAWA;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,aAAa;;;;;;yIAmDzB,CAAC"}

package/dist/index.cjs.js

@@ -12335,6 +12335,16 @@ const createChannel = async (bundle) => {
             /* c8 ignore next */
             isPublic: (bundle === null || bundle === void 0 ? void 0 : bundle.type) === 'community' ? isPublic : undefined }));
     }
+    // Fire the event locally, the same way createCommunity and createPost do.
+    // Without it a running getChannels collection never inserts the new channel:
+    // its query stream controller inserts an id only on OnCreate / OnJoin /
+    // OnResolveChannel / OnUnarchived, and the first sent message arrives as an
+    // OnUpdate, which only re-notifies. Reusing the MQTT event name means the
+    // already-wired onChannelCreated -> OnCreate path does the insert, so the
+    // list updates without a re-query. onChannelCreated re-runs
+    // prepareChannelPayload + ingestInCache itself, so this is idempotent with
+    // the ingest below.
+    fireEvent('channel.created', payload.data);
     const data = await prepareChannelPayload(payload.data);
     const cachedAt = client.cache && Date.now();
     if (client.cache)

package/dist/index.esm.js

@@ -12316,6 +12316,16 @@ const createChannel = async (bundle) => {
             /* c8 ignore next */
             isPublic: (bundle === null || bundle === void 0 ? void 0 : bundle.type) === 'community' ? isPublic : undefined }));
     }
+    // Fire the event locally, the same way createCommunity and createPost do.
+    // Without it a running getChannels collection never inserts the new channel:
+    // its query stream controller inserts an id only on OnCreate / OnJoin /
+    // OnResolveChannel / OnUnarchived, and the first sent message arrives as an
+    // OnUpdate, which only re-notifies. Reusing the MQTT event name means the
+    // already-wired onChannelCreated -> OnCreate path does the insert, so the
+    // list updates without a re-query. onChannelCreated re-runs
+    // prepareChannelPayload + ingestInCache itself, so this is idempotent with
+    // the ingest below.
+    fireEvent('channel.created', payload.data);
     const data = await prepareChannelPayload(payload.data);
     const cachedAt = client.cache && Date.now();
     if (client.cache)