dyte-io · tarushnagpal · Mar 7, 2025 · Mar 7, 2025
diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml
@@ -18,4 +18,4 @@ body:
     attributes:
       label: Proposed solution (optional)
       description: |
-        e.g. propose how the configuration of the new feature could look
+        e.g. propose how the configuration of the new feature could look
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -7,6 +7,7 @@ Describe your PR here.
 Closes #1
 
 ### Before submitting the PR, please take the following into consideration
+
 - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
 - [ ] Prefix your PR title with `feat: `, `fix: `, `chore: `, `docs:`, or `refactor:`.
 - [ ] The description should clearly illustrate what problems it solves.

diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
@@ -9,13 +9,13 @@ jobs:
   lint:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-node@v2
-      with:
-        node-version: 16
-        registry-url: https://registry.npmjs.org/
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 16
+          registry-url: https://registry.npmjs.org/
 
-    - name: npm install, lint
-      run: |
-        npm install
-        npm run lint
+      - name: npm install, lint
+        run: |
+          npm install
+          npm run lint
diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -1,3 +1,3 @@
 # Code of Conduct
 
-All Dyte repos are governed by our Community Participation Guidelines, available at: https://dyte.notion.site/dyte/Dyte-Community-Participation-Guidelines-CPG-4b3af58fdf3545c2a3065773a9154728
+All Dyte repos are governed by our Community Participation Guidelines, available at: https://dyte.notion.site/dyte/Dyte-Community-Participation-Guidelines-CPG-4b3af58fdf3545c2a3065773a9154728
diff --git a/bin/ui-kit/component-docs.cjs b/bin/ui-kit/component-docs.cjs
@@ -100,11 +100,11 @@ for (const component of components) {
 
   writeMDXFile(
     `${basePaths.react}/${tag}.mdx`,
-    generateFile(component, 'react')
+    generateFile(component, 'react'),
   );
 
   writeMDXFile(
     `${basePaths.angular}/${tag}.mdx`,
-    generateFile(component, 'angular')
+    generateFile(component, 'angular'),
   );
 }
diff --git a/bin/ui-kit/utils.cjs b/bin/ui-kit/utils.cjs
@@ -10,7 +10,7 @@ const { prettier: prettierConfig } = require('../../package.json');
 function writeMDXFile(path, text) {
   return fs.writeFileSync(
     path,
-    prettier.format(text, { ...prettierConfig, parser: 'mdx' })
+    prettier.format(text, { ...prettierConfig, parser: 'mdx' }),
   );
 }
 

diff --git a/bin/update-metadata.cjs b/bin/update-metadata.cjs
@@ -42,7 +42,7 @@ for (const section of Object.keys(prefixes)) {
       const headingMatch = content.match(/^# (.*)/m);
       if (!headingMatch && !existingTitle) {
         console.log(
-          `File ${filePath} does not have an H1 heading. Skipping...`
+          `File ${filePath} does not have an H1 heading. Skipping...`,
         );
         continue;
       }
@@ -66,7 +66,7 @@ for (const section of Object.keys(prefixes)) {
 
       const updatedFileContent = grayMatter.stringify(
         content + updatedContent.join('\n'),
-        data
+        data,
       );
       fs.writeFileSync(filePath, updatedFileContent);
 

diff --git a/cspell.json b/cspell.json
@@ -21,4 +21,4 @@
     "waitlisted",
     "htmlui"
   ]
-}
+}
diff --git a/docs/android-core/Introduction.mdx b/docs/android-core/Introduction.mdx
@@ -8,33 +8,33 @@ import ProductSection from '/docs/partials/_product-section.mdx';
 
 # Introduction
 
-The Dyte Core SDK is designed to provide you with an easy way to incorporate live video, voice, livestream and chat capabilities 
-into your Android apps. The Core SDK acts as a data-only layer. It provides simple APIs offering high-level primitives and 
+The Dyte Core SDK is designed to provide you with an easy way to incorporate live video, voice, livestream and chat capabilities
+into your Android apps. The Core SDK acts as a data-only layer. It provides simple APIs offering high-level primitives and
 abstracting away complex media and networking optimizations.
 
 ## Why Core SDK?
 
-The Core SDK was developed with a user-friendly approach to eliminate the complexity of managing streams. Unlike traditional 
-SDKs that require knowledge of WebRTC functioning, Dyte's Core SDK provides a simple API that abstracts out the complexity, 
-making it easier for developers to use. For instance, enabling video with Dyte's Core SDK is as easy as calling 
+The Core SDK was developed with a user-friendly approach to eliminate the complexity of managing streams. Unlike traditional
+SDKs that require knowledge of WebRTC functioning, Dyte's Core SDK provides a simple API that abstracts out the complexity,
+making it easier for developers to use. For instance, enabling video with Dyte's Core SDK is as easy as calling
 `meeting.localUser.enableVideo()`.
 
 ## Utility Modules
 
-The Core SDK includes various modules for in-call utilities like chat, polls, and recording that enable building a UI on top of 
+The Core SDK includes various modules for in-call utilities like chat, polls, and recording that enable building a UI on top of
 it. The following are the core SDK modules:
 
-- **meeting.localUser**: This consists of properties and methods corresponding to the current (local) user, such as enabling or 
-disabling their audio and video, getting a list of media devices or changing the device, or sharing your mobile screen.
-- **meeting.participants**: Use this module to get useful information about the other participants that are present in the 
-meeting. A host can use this module for access control. For example, the host can mute or kick a participant.
+- **meeting.localUser**: This consists of properties and methods corresponding to the current (local) user, such as enabling or
+  disabling their audio and video, getting a list of media devices or changing the device, or sharing your mobile screen.
+- **meeting.participants**: Use this module to get useful information about the other participants that are present in the
+  meeting. A host can use this module for access control. For example, the host can mute or kick a participant.
 - **meeting.chat**: It provides the methods to integrate chat features such as sending/receiving text, images, and files.
-- **meeting.polls**: Meetings can have polls. This module lets you perform actions related to polls, that is create and manage 
-a poll within a meeting.
-- **meeting.recording**: When a meeting needs to be recorded, this module can be used. It lets you start or stop a recording, 
-and get the current status of an ongoing recording.
-- **meeting.meta**: This object consists of all the metadata related to the current meeting, such as the title, the timestamp 
-of when it started, and more.
+- **meeting.polls**: Meetings can have polls. This module lets you perform actions related to polls, that is create and manage
+  a poll within a meeting.
+- **meeting.recording**: When a meeting needs to be recorded, this module can be used. It lets you start or stop a recording,
+  and get the current status of an ongoing recording.
+- **meeting.meta**: This object consists of all the metadata related to the current meeting, such as the title, the timestamp
+  of when it started, and more.
 - **meeting.plugins**: Provides the list of available plugins and active plugins. Use this module to enable or disable plugins as needed.
 
 <head>

diff --git a/docs/android-core/chat/introduction.mdx b/docs/android-core/chat/introduction.mdx
@@ -71,4 +71,4 @@ variables.
 
 <head>
   <title>Android Core Introducing chat</title>
-</head>
+</head>
diff --git a/docs/android-core/chat/receiving-chat-messages.mdx b/docs/android-core/chat/receiving-chat-messages.mdx
@@ -41,4 +41,4 @@ The `onMessageRateLimitReset()` method will be called when the rate limit for se
 
 <head>
   <title>Android Core Receiving chat</title>
-</head>
+</head>
diff --git a/docs/android-core/chat/sending-a-chat-message.mdx b/docs/android-core/chat/sending-a-chat-message.mdx
@@ -77,4 +77,4 @@ when (err) {
 
 <head>
   <title>Android Core Sending chat</title>
-</head>
+</head>
diff --git a/docs/android-core/livestream/dyte-livestream-listener.mdx b/docs/android-core/livestream/dyte-livestream-listener.mdx
@@ -116,5 +116,8 @@ This event is triggered when a stage request is rejected. The `peer` object cont
 
 <head>
   <title>Android Core Livestream Event Listeners</title>
-<meta name="description" content="Explore the functionalities and implementation of the Android Livestream Listener in Dyte documentation."/>
+  <meta
+    name="description"
+    content="Explore the functionalities and implementation of the Android Livestream Listener in Dyte documentation."
+  />
 </head>
diff --git a/docs/android-core/livestream/dyte-livestream-object.mdx b/docs/android-core/livestream/dyte-livestream-object.mdx
@@ -78,5 +78,8 @@ dyteMobileClient.livestream.rejectAll();
 
 <head>
   <title>Android Core Livestream Objects and Methods</title>
-  <meta name="description" content="Learn about the Android Livestream Object and its usage for effective livestream integration in your Android applications."/>
+  <meta
+    name="description"
+    content="Learn about the Android Livestream Object and its usage for effective livestream integration in your Android applications."
+  />
 </head>
diff --git a/docs/android-core/livestream/introduction.mdx b/docs/android-core/livestream/introduction.mdx
@@ -17,5 +17,8 @@ The foundation of Dyte's livestreaming is based on a stage, which can be accesse
 
 <head>
   <title>Android Core Introduction</title>
-  <meta name="description" content="Get started with Android Livestreaming through this comprehensive introduction guide in Dyte Docs."/>
+  <meta
+    name="description"
+    content="Get started with Android Livestreaming through this comprehensive introduction guide in Dyte Docs."
+  />
 </head>
diff --git a/docs/android-core/local-user/events.mdx b/docs/android-core/local-user/events.mdx
@@ -74,7 +74,6 @@ meeting.addSelfEventsListener(object : DyteSelfEventsListener {
 })
 ```
 
-
   </TabItem>
 
   <TabItem value="java" label="Java" default>
@@ -91,7 +90,6 @@ meeting.addSelfEventsListener(new DyteSelfEventsListener() {
 });
 ```
 
-
   </TabItem>
 </Tabs>
 
@@ -119,7 +117,6 @@ WaitListStatus waitListStatus = meeting.localUser.getWaitListStatus();
   </TabItem>
 </Tabs>
 
-
 You can listen to those changes in `onWaitListStatusUpdate()` callbacks
 
 <Tabs groupId="android-core-local-user">

diff --git a/docs/android-core/local-user/introduction.mdx b/docs/android-core/local-user/introduction.mdx
@@ -63,7 +63,6 @@ DyteMeetingInfoV2 meetingInfo = new DyteMeetingInfoV2(
   </TabItem>
 </Tabs>
 
-
 ## Get local user video view
 
 To display the `localUser` preview in a view, utilize the `getSelfPreview()` method on `localUser`. This method provides a View that can be added to any `ViewGroup` in Android.
@@ -141,7 +140,6 @@ meeting.localUser.enableAudio(error -> null);
   </TabItem>
 </Tabs>
 
-
 ## Enable/disable camera
 
 Enable/disable your camera in the meeting using `disableVideo()` and `enableVideo()` methods, and check the current status with `videoEnabled`.
@@ -177,13 +175,11 @@ meeting.localUser.enableVideo(error -> null);
   </TabItem>
 </Tabs>
 
-
 ## Enable / Disable Screen share
 
 :::tip Note
 To use screenshare on Android devices running Android API 14 and above, you will need to declare the following permission in your app's AndroidManifest.xml.
 
-
 `<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION" />`
 
 Adding above permission will require you to do extra steps on Google Play Console while submitting the app. For more information please refer [this](https://support.google.com/googleplay/android-developer/answer/13392821?hl=en#declare).

diff --git a/docs/android-core/local-user/manage-media-devices.mdx b/docs/android-core/local-user/manage-media-devices.mdx
@@ -89,5 +89,8 @@ meeting.getLocalUser().setVideoDevice(device);
 
 <head>
   <title>Android Core Manage Media Devices</title>
-  <meta name="description" content="Effectively manage media devices on Android using Dyte's documentation, ensuring seamless user experiences."/>
+  <meta
+    name="description"
+    content="Effectively manage media devices on Android using Dyte's documentation, ensuring seamless user experiences."
+  />
 </head>
diff --git a/docs/android-core/local-user/manage-permissions.mdx b/docs/android-core/local-user/manage-permissions.mdx
@@ -76,5 +76,8 @@ meeting.addSelfEventsListener(new : DyteSelfEventsListener() {
 
 <head>
   <title>Android Core Media Permissions</title>
-  <meta name="description" content="Learn how to manage permissions in your Android application for a secure and controlled user experience with Dyte Docs."/>
+  <meta
+    name="description"
+    content="Learn how to manage permissions in your Android application for a secure and controlled user experience with Dyte Docs."
+  />
 </head>
diff --git a/docs/android-core/participants/events.mdx b/docs/android-core/participants/events.mdx
@@ -61,7 +61,6 @@ Triggers an event when any participant leaves the meeting.
     }
 ```
 
-
   </TabItem>
 
   <TabItem value="java" label="Java" default>
@@ -74,11 +73,9 @@ Triggers an event when any participant leaves the meeting.
     };
 ```
 
-
   </TabItem>
 </Tabs>
 
-
 ### Participants update
 
 Triggers an event whenever there is any change in the `meeting.participants` object. This includes any updates to participant lists or changes in individual participant within those lists.
@@ -117,13 +114,13 @@ Triggers an event when any participant starts / stops video.
 <Tabs groupId="android-core-participants">
   <TabItem value="kotlin" label="Kotlin" default>
 
-  ```kotlin
-      private val participantEventsListener = object : DyteParticipantsEventListener {
-          override fun onVideoUpdate(participant: DyteRemoteParticipant, isEnabled: Boolean) {
-              // your code here to handle participant video toggle update
-          }
-      }
-  ```
+```kotlin
+    private val participantEventsListener = object : DyteParticipantsEventListener {
+        override fun onVideoUpdate(participant: DyteRemoteParticipant, isEnabled: Boolean) {
+            // your code here to handle participant video toggle update
+        }
+    }
+```
 
   </TabItem>
 
@@ -141,7 +138,6 @@ Triggers an event when any participant starts / stops video.
   </TabItem>
 </Tabs>
 
-
 ### Audio update
 
 Triggers an event when any participant starts / stops audio.
@@ -254,7 +250,6 @@ Triggers an event when there is any change in pinned participant in the meeting.
     }
 ```
 
-
   </TabItem>
 
   <TabItem value="java" label="Java" default>
@@ -316,26 +311,26 @@ Triggers an event whenever there is any change in participant.
 <Tabs groupId="android-core-participants">
   <TabItem value="kotlin" label="Kotlin" default>
 
-  ```kotlin
-      private val participantUpdateListener = object : DyteParticipantUpdateListener {
-          override fun onUpdate(participant: DyteRemoteParticipant) {
-              // your code here to handle participant update
-          }
-      }
-  ```
+```kotlin
+    private val participantUpdateListener = object : DyteParticipantUpdateListener {
+        override fun onUpdate(participant: DyteRemoteParticipant) {
+            // your code here to handle participant update
+        }
+    }
+```
 
   </TabItem>
 
   <TabItem value="java" label="Java" default>
 
-  ```java
-      DyteParticipantUpdateListener participantUpdateListener = new DyteParticipantUpdateListener() {
-          @Override
-          public void onUpdate(DyteRemoteParticipant participant) {
-              // your code here to handle participant update
-          }
-      }
-  ```
+```java
+    DyteParticipantUpdateListener participantUpdateListener = new DyteParticipantUpdateListener() {
+        @Override
+        public void onUpdate(DyteRemoteParticipant participant) {
+            // your code here to handle participant update
+        }
+    }
+```
 
   </TabItem>
 </Tabs>
@@ -369,8 +364,6 @@ Triggers an event when the participant starts / stops video.
   </TabItem>
 </Tabs>
 
-
-
 ### Audio update
 
 Triggers an event when the participant starts / stops audio.
@@ -402,7 +395,6 @@ Triggers an event when the participant starts / stops audio.
   </TabItem>
 </Tabs>
 
-
 ### Pinned & Unpinned participant
 
 Triggers an event when the participant is pinned / unpinned.
@@ -443,7 +435,6 @@ Triggers an event when the participant is pinned / unpinned.
   </TabItem>
 </Tabs>
 
-
 ### Screen share started & ended
 
 Triggers an event when the participant starts / stops screen sharing.

diff --git a/docs/android-core/participants/participant-object.mdx b/docs/android-core/participants/participant-object.mdx
@@ -138,7 +138,6 @@ participant.ifPresent(pcpt -> {
 You can also `pin` or `unpin` a participant in the meeting. All "pinned"
 participants are added to the `meeting.participants.pinned` list.
 
-
 <Tabs groupId="android-core-participants">
   <TabItem value="kotlin" label="Kotlin" default>
-Original file line number
+Diff line change
@@ Expand Up / @@ -21,4 +21,4 @@ @@
         "waitlisted",
         "htmlui"
       ]
-    }
+    }