SCAL-256912 Enhance error handling by introducing EmbedErrorEvent interface #329

shivam-kumar-ts · 2025-10-12T23:44:41Z

Enhance error handling in TsEmbed and related components by introducing EmbedErrorEvent interface.
Update error handling to use structured error objects for validation and API errors across various embed classes.

mnk-blr · 2025-10-12T23:44:53Z

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

gemini-code-assist · 2025-10-12T23:44:59Z

Summary of Changes

Hello @shivam-kumar-ts, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the error handling mechanism within the SDK by introducing a standardized EmbedErrorEvent interface. This change ensures that all errors emitted by the SDK are structured consistently, providing richer context such as errorType, code, source, and details. This standardization improves the clarity and debuggability of error events for consumers of the SDK, making it easier to understand and respond to issues.

Highlights

Standardized Error Interface: Introduced a new EmbedErrorEvent interface to standardize the structure of error objects emitted by the SDK, providing consistent properties like errorType, message, code, source, and details.
Refactored Error Handling: The handleError method in TsEmbed and related components has been refactored to accept and process these new structured EmbedErrorEvent objects, replacing previous calls that used simple strings or generic objects.
Consistent Error Reporting: Updated error handling logic across ConversationEmbed, LiveboardEmbed, and TsEmbed to construct and pass EmbedErrorEvent objects for various validation and API-related errors, ensuring uniform error reporting.
Expanded Error Messages: New, specific error messages have been added to the ERROR_MESSAGE constants for common validation and operational issues, improving clarity.
Updated Documentation: The JSDoc for EmbedEvent.Error has been updated to reflect the new structured error object format and provide clearer examples for developers.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request is a great step towards more robust error handling by introducing the EmbedErrorEvent interface. The transition from string-based errors to structured error objects is well-executed across the affected components. My feedback focuses on enhancing this new structure by improving consistency in error handling logic, increasing the specificity of error codes for better diagnostics, and ensuring the semantic correctness of error types.

gemini-code-assist · 2025-10-12T23:46:23Z

src/embed/ts-embed.ts

            this.executeCallbacks(EmbedEvent.Error, {
-                offlineWarning,
-            });
-            logger.warn(offlineWarning);
+                errorType: 'API',
+                message: ERROR_MESSAGE.OFFLINE_WARNING,
+                code: 'NETWORK_ERROR',
+                source: 'SDK',
+                details: {
+                    event: e,
+                },
+                error: ERROR_MESSAGE.OFFLINE_WARNING,
+            } as EmbedErrorEvent);
+            logger.warn(ERROR_MESSAGE.OFFLINE_WARNING);


For consistency with other error handling in this class, it would be better to use this.handleError() here instead of calling this.executeCallbacks() directly. The current implementation doesn't set this.isError = true, which might lead to inconsistent state. Using handleError will also centralize error logging.

Additionally, since this is a network-related event, consider changing the source from 'SDK' to 'NETWORK' to be more descriptive.

Note that handleError uses logger.error, while the original code used logger.warn. This change seems appropriate for an offline event, but please confirm if this is the desired behavior.

Suggested change

this.executeCallbacks(EmbedEvent.Error, {

offlineWarning,

});

logger.warn(offlineWarning);

errorType: 'API',

message: ERROR_MESSAGE.OFFLINE_WARNING,

code: 'NETWORK_ERROR',

source: 'SDK',

details: {

event: e,

},

error: ERROR_MESSAGE.OFFLINE_WARNING,

} as EmbedErrorEvent);

logger.warn(ERROR_MESSAGE.OFFLINE_WARNING);

this.handleError({

errorType: 'API',

message: ERROR_MESSAGE.OFFLINE_WARNING,

code: 'NETWORK_ERROR',

source: 'NETWORK',

details: {

event: e,

},

error: ERROR_MESSAGE.OFFLINE_WARNING,

} as EmbedErrorEvent);

gemini-code-assist · 2025-10-12T23:46:23Z

src/embed/ts-embed.ts

+            this.handleError({
+                errorType: 'VALIDATION_ERROR',
+                message: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,
+                code: 'VALIDATION_ERROR',
+                source: 'SDK',
+                details: {},
+                error: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,
+            } as EmbedErrorEvent);


The code property in the error object is set to 'VALIDATION_ERROR', which is the same as errorType. To make error diagnostics more precise, it's better to use a more specific error code. Consider using 'CONFLICTING_ACTIONS_CONFIG' for the code. This will also require updating the corresponding test expectations.

Suggested change

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,

code: 'VALIDATION_ERROR',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,

} as EmbedErrorEvent);

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,

code: 'CONFLICTING_ACTIONS_CONFIG',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,

} as EmbedErrorEvent);

gemini-code-assist · 2025-10-12T23:46:23Z

src/embed/ts-embed.ts

+            this.handleError({
+                errorType: 'VALIDATION_ERROR',
+                message: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,
+                code: 'VALIDATION_ERROR',
+                source: 'SDK',
+                details: {},
+                error: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,
+            } as EmbedErrorEvent);


Similar to the conflicting actions error, the code here is 'VALIDATION_ERROR', which is redundant with errorType. Using a more specific code like 'CONFLICTING_TABS_CONFIG' would improve error identification. Remember to update the related tests.

Suggested change

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,

code: 'VALIDATION_ERROR',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,

} as EmbedErrorEvent);

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,

code: 'CONFLICTING_TABS_CONFIG',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.CONFLICTING_TABS_CONFIG,

} as EmbedErrorEvent);

gemini-code-assist · 2025-10-12T23:46:23Z

src/embed/ts-embed.ts

+            this.handleError({
+                errorType: 'INVALID_OPERATOR',
+                message: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,
+                code: 'RENDER_NOT_CALLED',
+                source: 'SDK',
+                details: {},
+                error: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,
+            } as EmbedErrorEvent);


The errorType is set to 'INVALID_OPERATOR'. According to the documentation for EmbedEvent.Error, this type is intended for errors related to filter operators. Since this error is about calling trigger before render, a more semantically correct errorType would be 'VALIDATION_ERROR'. This would better reflect that it's a state validation failure.

Suggested change

this.handleError({

errorType: 'INVALID_OPERATOR',

message: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,

code: 'RENDER_NOT_CALLED',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,

} as EmbedErrorEvent);

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,

code: 'RENDER_NOT_CALLED',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.RENDER_BEFORE_EVENTS_REQUIRED,

} as EmbedErrorEvent);

gemini-code-assist · 2025-10-12T23:46:24Z

src/embed/conversation.ts

+            this.handleError({
+                errorType: 'VALIDATION_ERROR',
+                message: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,
+                code: 'VALIDATION_ERROR',
+                source: 'SDK',
+                details: {},
+                error: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,
+            } as EmbedErrorEvent);


The code property is set to 'VALIDATION_ERROR', which is the same as errorType. For better error diagnostics, consider using a more specific code, such as 'WORKSHEET_ID_NOT_FOUND'. This will require an update to the test expectations in src/embed/conversation.spec.ts.

Suggested change

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,

code: 'VALIDATION_ERROR',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,

} as EmbedErrorEvent);

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,

code: 'WORKSHEET_ID_NOT_FOUND',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND,

} as EmbedErrorEvent);

gemini-code-assist · 2025-10-12T23:46:24Z

src/embed/liveboard.ts

+            this.handleError({
+                errorType: 'VALIDATION_ERROR',
+                message: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,
+                code: 'VALIDATION_ERROR',
+                source: 'SDK',
+                details: {},
+                error: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,
+            } as EmbedErrorEvent);


The code property is set to 'VALIDATION_ERROR', which is redundant as it's the same as errorType. A more specific code like 'LIVEBOARD_ID_MISSING' would be more helpful for debugging. Please update any relevant tests if they exist.

Suggested change

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,

code: 'VALIDATION_ERROR',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,

} as EmbedErrorEvent);

this.handleError({

errorType: 'VALIDATION_ERROR',

message: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,

code: 'LIVEBOARD_ID_MISSING',

source: 'SDK',

details: {},

error: ERROR_MESSAGE.LIVEBOARD_VIZ_ID_VALIDATION,

} as EmbedErrorEvent);

pkg-pr-new · 2025-10-12T23:46:55Z

Open in StackBlitz

npm i https://pkg.pr.new/thoughtspot/visual-embed-sdk/@thoughtspot/visual-embed-sdk@329

commit: 1d83508

adityamittal3107 · 2025-11-05T06:20:12Z

src/embed/ts-embed.ts

        });
        // Log error
        logger.error(error);
+        logger.error(errorDetails);


We can remove this.

adityamittal3107 · 2025-11-05T13:16:44Z

src/embed/ts-embed.ts

                offlineWarning,
            });
-            logger.warn(offlineWarning);
+            const errorDetails = { errorType: 'API', message: ERROR_MESSAGE.OFFLINE_WARNING, code: ERROR_CODE.NETWORK_ERROR, source: 'NETWORK', details: { event: e, } } as EmbedErrorDetailsEvent;


how is this api type? maybe we can have network in the error type

I think offline, so api failed so added it
so should i remove it?

sastaachar · 2025-11-07T11:00:21Z

src/types.ts

+ * @version SDK: 1.44.0 | ThoughtSpot: 26.2.0.cl
+ */
+export interface EmbedErrorDetailsEvent {
+    errorType: 'API' | 'FULLSCREEN' | 'SINGLE_VALUE_FILTER' | 'NON_EXIST_FILTER' | 'INVALID_DATE_VALUE' | 'INVALID_OPERATOR' | 'VALIDATION_ERROR' | string;


dont allow string

in Embed.Error this six types are there so i added here along with string

sastaachar · 2025-11-07T11:00:26Z

src/types.ts

+    errorType: 'API' | 'FULLSCREEN' | 'SINGLE_VALUE_FILTER' | 'NON_EXIST_FILTER' | 'INVALID_DATE_VALUE' | 'INVALID_OPERATOR' | 'VALIDATION_ERROR' | string;
+    message: string | string[];
+    code: string;
+    source?: 'API' | 'NETWORK' | 'SDK';


in Embed.Error this six types are there so i added here along with string

sastaachar · 2025-11-07T11:01:27Z

src/types.ts

+ * @version SDK: 1.44.0 | ThoughtSpot: 26.2.0.cl
+ */
+export interface EmbedErrorDetailsEvent {
+    errorType: 'API' | 'FULLSCREEN' | 'SINGLE_VALUE_FILTER' | 'NON_EXIST_FILTER' | 'INVALID_DATE_VALUE' | 'INVALID_OPERATOR' | 'VALIDATION_ERROR' | string;


dont allow string

sastaachar · 2025-11-07T11:03:15Z

src/types.ts

+ * @param message - A human-readable error message describing what went wrong.
+ * @param code - Error code providing a machine-readable identifier for the error.
+ * @param source - The source system or component where the error originated.
+ * @param details - Additional error details providing context-specific information.


why is error code needed ? what is diff btw that an error type

Error code is unique and error type is a type which error belong to

src/types.ts

sastaachar · 2025-11-07T11:04:38Z

src/embed/ts-embed.spec.ts

+                errorType: 'VALIDATION_ERROR',
+                message: ERROR_MESSAGE.CONFLICTING_ACTIONS_CONFIG,
+                code: ERROR_CODE.CONFLICTING_ACTIONS_CONFIG,
+                source: 'SDK',


where else will embed event error come from ? isnt this pointless ?

sastaachar · 2025-11-07T11:05:39Z

src/types.ts

+    errorType: 'API' | 'FULLSCREEN' | 'SINGLE_VALUE_FILTER' | 'NON_EXIST_FILTER' | 'INVALID_DATE_VALUE' | 'INVALID_OPERATOR' | 'VALIDATION_ERROR' | string;
+    message: string | string[];
+    code: string;
+    source?: 'API' | 'NETWORK' | 'SDK';


why is this needed ? wont error type resolve this ?

No, source give the information of that in come from api or sdk

ok but as a customer what will i do with this info ?

sastaachar · 2025-11-18T06:12:21Z

src/embed/conversation.ts

        if (!worksheetId) {
-            this.handleError(ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND);
+            this.handleError(ERROR_MESSAGE.SPOTTER_EMBED_WORKSHEED_ID_NOT_FOUND, {
+                errorType: ErrorDetailsTypes.VALIDATION_ERROR,


why is errorType and code both needed ? what is the use for source here ?
from customer's point of view arent all errors from sdk

sastaachar · 2025-11-18T06:12:53Z

src/embed/ts-embed.ts

+            code: ERROR_CODE.INIT_ERROR,
+            source: ErrorDetailsSources.SDK,
+            details: {},
+        } as EmbedErrorDetailsEvent);


why is as needed here ?

sastaachar · 2025-11-18T06:20:42Z

src/types.ts

+     * })
+     * ```
+     */
+    ErrorDetails = 'ErrorDetails',


why do we need a new embed event, the ticket says to improve the exiting event payload, whats the benefit of new event on its own ?

sastaachar · 2025-11-18T06:21:46Z

src/types.ts

+export enum ErrorDetailsSources {
+    API = 'API',


what are the use cases for this ? this might confuse customers imo

adityamittal3107 · 2025-11-21T10:01:34Z

src/types.ts

+ * - **Liveboard ID missing**: Errors related to missing liveboard ID
+ * - **Conflicting actions configuration**: Errors related to conflicting actions configuration
+ * - **Conflicting tabs configuration**: Errors related to conflicting tabs configuration
+ * - **Initialization error**: Errors related to initialization error


error description is added below as well. No need to add it twice.

…ent interface

…erface

…and remove unused ones

…enum

…h standardized error

sonar-prod-ts · 2025-11-22T09:19:41Z

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication

shivam-kumar-ts requested a review from a team as a code owner October 12, 2025 23:44

gemini-code-assist bot reviewed Oct 12, 2025

View reviewed changes

shivam-kumar-ts force-pushed the SCAL-256912 branch 8 times, most recently from b68c845 to 3301d3e Compare October 29, 2025 06:04

shivam-kumar-ts force-pushed the SCAL-256912 branch 2 times, most recently from fa1049d to 7b478a3 Compare November 5, 2025 01:54

adityamittal3107 reviewed Nov 5, 2025

View reviewed changes

src/embed/ts-embed.ts

});

// Log error

logger.error(error);

logger.error(errorDetails);

Copy link

Contributor

adityamittal3107 Nov 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove this.

shivam-kumar-ts force-pushed the SCAL-256912 branch from a619520 to 31adaa6 Compare November 5, 2025 08:58

adityamittal3107 reviewed Nov 5, 2025

View reviewed changes

sastaachar reviewed Nov 7, 2025

View reviewed changes

shivam-kumar-ts force-pushed the SCAL-256912 branch from 6bae6b5 to 4b19aec Compare November 8, 2025 04:48

shivam-kumar-ts force-pushed the SCAL-256912 branch from b6de516 to 482b3a0 Compare November 17, 2025 18:26

sastaachar reviewed Nov 18, 2025

View reviewed changes

adityamittal3107 reviewed Nov 21, 2025

View reviewed changes

shivam-kumar-ts added 5 commits November 22, 2025 13:33

SCAL-256912 Enhance error handling by introducing EmbedErrorDetailsEv…

bcb0070

…ent interface

SCAL-256912 updated the error message type

c0b94f9

SCAL-256912 removed duplicate logger

5f4aea0

SCAL-256912 added test to increase the coverage

bfbfd55

SCAL-256912 updated error type

412a7a6

shivam-kumar-ts added 12 commits November 22, 2025 13:33

SCAL-256912 introduced EmbedErrorType and EmbedErrorSource enums

ac2c6f7

SCAL-256912 updated ErrorDetailsTypes enum

6bacb4e

SCAL-256912 rebase with main

6a05344

SCAL-256912 Remove ErrorDetailsSources enum and its usage

67c4a6f

SCAL-256912 Remove unused details property from error objects

c398505

SCAL-256912 Refactor error handling to use EmbedErrorDetailsEvent int…

98f994d

…erface

SCAL-256912 Introduce EmbedErrorCodes enum

dcc8a61

SCAL-256912 Refactor EmbedErrorCodes enum to include new error codes …

d89eded

…and remove unused ones

SCAL-256912 Remove unused error details types from ErrorDetailsTypes …

5b7aab8

…enum

SCAL-256912 Remove unused error types from EmbedEvent enum

2cd1a03

SCAL-256912 rebase with main

c0609f7

SCAL-256912 Enhance error handling for API intercept body parsing wit…

5488d1b

…h standardized error

shivam-kumar-ts force-pushed the SCAL-256912 branch from 68a6d66 to 5488d1b Compare November 22, 2025 08:58

SCAL-256912 Improve error logging for API intercept body parsing

1d83508

SCAL-256912 Enhance error handling by introducing EmbedErrorEvent interface #329

Are you sure you want to change the base?

SCAL-256912 Enhance error handling by introducing EmbedErrorEvent interface #329

Conversation

shivam-kumar-ts commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mnk-blr commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Snyk checks have passed. No issues have been found so far.

Uh oh!

gemini-code-assist bot commented Oct 12, 2025

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Oct 12, 2025

Choose a reason for hiding this comment

Uh oh!

pkg-pr-new bot commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

adityamittal3107 Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shivam-kumar-ts Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shivam-kumar-ts commented Oct 12, 2025 •

edited

Loading

mnk-blr commented Oct 12, 2025 •

edited

Loading

pkg-pr-new bot commented Oct 12, 2025 •

edited

Loading

adityamittal3107 Nov 5, 2025 •

edited

Loading

shivam-kumar-ts Nov 7, 2025 •

edited

Loading