Added Error handling as tabs were not rendering data on sudden switch…

[kaushikakshay-ctrl]

…ing of tabs

[gemini-code-assist]

Summary of Changes

Hello @kaushikakshay-ctrl, 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 improves the backend's error handling capabilities by introducing a robust mechanism to catch and process errors originating from asynchronous operations within API routes. By centralizing error capture and providing a standardized JSON error response, the changes aim to prevent application crashes and ensure a more predictable experience, especially in scenarios where frontend components might fail to render data due to unhandled backend exceptions.

Highlights

• Centralized Async Error Handling: Introduced a catchAsync utility function to wrap asynchronous Express route handlers, ensuring that any unhandled promise rejections are automatically caught and passed to the error-handling middleware.
• API Route Error Integration: Applied the new catchAsync utility to all existing API routes in api.js (e.g., /embed-user/token, /sso-url, /me, /looks, /looks/:id), standardizing error capture across the API.
• Global Error Middleware: Implemented a global error-handling middleware in server.js to process errors caught by catchAsync. This middleware formats errors into a consistent JSON response, including a status code and message, improving client-side error management.

🧠 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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a catchAsync utility to centralize error handling in your Express routes, which is a great step towards more robust code. My review focuses on a few critical and high-severity issues that prevent this new error handling mechanism from working as intended. Specifically, the global error handler in server.js has an incorrect signature, and several routes in api.js still contain local .catch() blocks that swallow errors, bypassing the new catchAsync wrapper. Addressing these points will ensure that errors are consistently caught and handled.