update shard info config for js-waku

docs/guides/js-waku/light-send-receive.md

@@ -24,6 +24,19 @@ await node.start();
 When the `defaultBootstrap` parameter is set to `true`, your node will be bootstrapped using the [default bootstrap method](/guides/js-waku/configure-discovery#default-bootstrap-method). Have a look at the [Bootstrap Nodes and Discover Peers](/guides/js-waku/configure-discovery) guide to learn more methods to bootstrap nodes.
 :::
 
+By default, your node will route messages to the standard pubsub topic (`/waku/2/default-waku/proto`). If your project uses a different shared pubsub topic, you can configure this using the `ShardInfo` parameter:
+
+```js
+// Create the shard info
+const shardInfo = { clusterId: 3, shards: [1, 2] };
+
+// Create node with custom shard info
+const node = await createLightNode({
+  defaultBootstrap: true,
+  shardInfo: shardInfo,
+});
+```
+
 ## Connect to remote peers
 
 Use the `waitForRemotePeer()` function to wait for the node to connect with peers on the Waku Network:
@@ -41,10 +54,7 @@ The `protocols` parameter allows you to specify the [protocols](/learn/concepts/
 import { waitForRemotePeer, Protocols } from "@waku/sdk";
 
 // Wait for peer connections with specific protocols
-await waitForRemotePeer(node, [
-	Protocols.LightPush,
-	Protocols.Filter,
-]);
+await waitForRemotePeer(node, [Protocols.LightPush, Protocols.Filter]);
 ```
 
 ## Choose a content topic
@@ -66,11 +76,25 @@ The `ephemeral` parameter allows you to specify whether messages should **NOT**
 
 ```js
 const encoder = createEncoder({
-	contentTopic: contentTopic, // message content topic
-	ephemeral: true, // allows messages NOT be stored on the network
+  contentTopic: contentTopic, // message content topic
+  ephemeral: true, // allows messages NOT be stored on the network
 });
 ```
 
+The `pubsubTopicShardInfo` parameter allows you to configure a different shared pubsub topic for your `encoder` and `decoder`:
+
+```js
+// Create the shard info
+const shardInfo = { clusterId: 3, shard: 1 };
+
+// Create encoder and decoder with custom shard info
+const encoder = createEncoder({
+  contentTopic: contentTopic,
+  pubsubTopicShardInfo: shardInfo,
+});
+const decoder = createDecoder(contentTopic, shardInfo);
+```
+
 :::info
 In this example, users send and receive messages on a shared content topic. However, real applications may have users broadcasting messages while others listen or only have 1:1 exchanges. Waku supports all these use cases.
 :::
@@ -84,9 +108,9 @@ import protobuf from "protobufjs";
 
 // Create a message structure using Protobuf
 const ChatMessage = new protobuf.Type("ChatMessage")
-    .add(new protobuf.Field("timestamp", 1, "uint64"))
-    .add(new protobuf.Field("sender", 2, "string"))
-    .add(new protobuf.Field("message", 3, "string"));
+  .add(new protobuf.Field("timestamp", 1, "uint64"))
+  .add(new protobuf.Field("sender", 2, "string"))
+  .add(new protobuf.Field("message", 3, "string"));
 ```
 
 :::info
@@ -100,17 +124,17 @@ To send messages over the Waku Network using the `Light Push` protocol, create a
 ```js
 // Create a new message object
 const protoMessage = ChatMessage.create({
-    timestamp: Date.now(),
-    sender: "Alice",
-    message: "Hello, World!",
+  timestamp: Date.now(),
+  sender: "Alice",
+  message: "Hello, World!",
 });
 
 // Serialise the message using Protobuf
 const serialisedMessage = ChatMessage.encode(protoMessage).finish();
 
 // Send the message using Light Push
 await node.lightPush.send(encoder, {
-    payload: serialisedMessage,
+  payload: serialisedMessage,
 });
 ```
 
@@ -121,11 +145,11 @@ To receive messages using the `Filter` protocol, create a callback function for
 ```js
 // Create the callback function
 const callback = (wakuMessage) => {
-    // Check if there is a payload on the message
-    if (!wakuMessage.payload) return;
-    // Render the messageObj as desired in your application
-    const messageObj = ChatMessage.decode(wakuMessage.payload);
-    console.log(messageObj);
+  // Check if there is a payload on the message
+  if (!wakuMessage.payload) return;
+  // Render the messageObj as desired in your application
+  const messageObj = ChatMessage.decode(wakuMessage.payload);
+  console.log(messageObj);
 };
 
 // Create a Filter subscription
@@ -135,6 +159,16 @@ const subscription = await node.filter.createSubscription();
 await subscription.subscribe([decoder], callback);
 ```
 
+The `pubsubTopicShardInfo` parameter allows you to configure a different shared pubsub topic for your `Filter` subscription:
+
+```js
+// Create the shard info
+const shardInfo = { clusterId: 3, shard: 1 };
+
+// Create Filter subscription with custom shard info
+const subscription = await node.filter.createSubscription(shardInfo);
+```
+
 You can use the `subscription.unsubscribe()` function to stop receiving messages from a content topic:
 
 ```js
@@ -143,4 +177,4 @@ await subscription.unsubscribe([contentTopic]);
 
 :::tip Congratulations!
 You have successfully sent and received messages over the Waku Network using the `Light Push` and `Filter` protocols. Have a look at the [light-js](https://github.com/waku-org/js-waku-examples/tree/master/examples/light-js) and [light-chat](https://github.com/waku-org/js-waku-examples/tree/master/examples/light-chat) examples for working demos.
-:::
+:::