Skip to content

Conversation

@ruchI9897
Copy link
Contributor

No description provided.

@ruchI9897 ruchI9897 requested a review from a team as a code owner December 18, 2025 06:49
@mnk-blr
Copy link
Collaborator

mnk-blr commented Dec 18, 2025

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
Copy link
Contributor

Summary of Changes

Hello @ruchI9897, I'm Gemini Code Assist1! 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 introduces a robust token refresh mechanism to enhance the user experience in embedded applications. By proactively fetching new authentication tokens when existing ones are nearing expiry, it ensures continuous authentication for cookieless trusted authentication scenarios, thereby preventing session timeouts and maintaining an uninterrupted user session.

Highlights

  • Token Refresh Mechanism: A new tokenRefresh method has been implemented to handle the process of refreshing authentication tokens, specifically for TrustedAuthTokenCookieless authentication when autoLogin is enabled.
  • Enhanced getAuthenticationToken: The getAuthenticationToken function now includes an optional getFreshToken parameter, allowing callers to explicitly request a new token and bypass the cached one.
  • New Embed Event: A new EmbedEvent.RefreshAuthToken has been introduced. This event is emitted when an authentication token is about to expire, triggering the new token refresh logic.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Footnotes

  1. 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a mechanism for refreshing authentication tokens, primarily for cookieless authentication. The changes include adding a getFreshToken parameter to getAuthenticationToken, defining a new RefreshAuthToken embed event, and implementing the tokenRefresh handler to fetch and provide a new token when requested.

My review focuses on improving the maintainability of the new tokenRefresh method. I've suggested adding proper types to its parameters to enhance type safety and pointed out code duplication with the existing updateAuthToken method, recommending a refactor to a shared helper function. These changes will make the code cleaner and easier to maintain.

* @param _
* @param responder
*/
private tokenRefresh = async (_: any, responder: any) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better type safety and code clarity, consider providing specific types for the _ and responder parameters instead of any. Based on the on method signature, _ can be typed as MessagePayload and responder as (data: any) => void. You'll need to import MessagePayload from ../types.

Suggested change
private tokenRefresh = async (_: any, responder: any) => {
private tokenRefresh = async (_: MessagePayload, responder: (data: any) => void) => {

Comment on lines +519 to +528
try {
const authToken = await getAuthenticationToken(this.embedConfig, true);
responder({
type: EmbedEvent.RefreshAuthToken,
data: { authToken },
});
} catch (e) {
logger.error(`${ERROR_MESSAGE.INVALID_TOKEN_ERROR} Error : ${e?.message}`);
processAuthFailure(e, this.isPreRendered ? this.preRenderWrapper : this.el);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This try...catch block is nearly identical to the one in the updateAuthToken method (lines 544-553). To improve code maintainability and adhere to the DRY (Don't Repeat Yourself) principle, consider extracting this logic into a shared private helper method. This helper could take parameters for getFreshToken and the EmbedEvent type to handle the minor differences between the two usages.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 18, 2025

Open in StackBlitz

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

commit: 5ece501

@sonar-prod-ts
Copy link

sonar-prod-ts bot commented Dec 22, 2025

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants