Skip to content

Conversation

@Chaitu7032
Copy link
Contributor

  • Implement floating chatbot UI component with modern design
  • Add backend chatbot API with stock analysis capabilities
  • Integrate real-time stock data processing and mock data
  • Add technical analysis features (RSI, moving averages)
  • Provide AI-powered investment recommendations
  • Support natural language stock symbol recognition
  • Add responsive chat interface with stock data visualization
  • Include comprehensive error handling and fallbacks
  • Add environment configuration for API integrations
  • Create test scripts and documentation

Features:

  • Floating blue chat icon in bottom-right corner
  • Interactive chat window with typing indicators

@vercel
Copy link

vercel bot commented Sep 23, 2025

@Chaitu7032 is attempting to deploy a commit to the mihir2006's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link

Thanks for creating this PR

We'll review it as soon as possible.
In the meantime, please double-check the file changes and ensure that all commits are accurate.

If there are any unresolved review comments, feel free to resolve them.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Chaitu7032, 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 new AI-powered stock analyzer chatbot feature, enhancing the application's capabilities for investment recommendations and real-time stock data processing. The changes involve setting up the necessary backend infrastructure, including flexible database options and new external API integrations, and integrating an interactive chatbot user interface into the frontend.

Highlights

  • Database Flexibility: The backend database configuration has been updated to support SQLite as a default option, providing a more flexible setup for development and local environments without requiring a PostgreSQL instance.
  • New API Integrations: Environment variables for Polygon and Finnhub API keys have been added to the example configuration, indicating the integration of new external data sources for comprehensive stock analysis.
  • Chatbot Backend Integration: A dedicated 'chatbot' router has been introduced and integrated into the FastAPI application, establishing the backend infrastructure for the AI-powered stock analyzer chatbot.
  • Chatbot Frontend Integration: A new 'Chatbot' UI component is now imported and rendered within the main application layout, making the interactive chatbot accessible to users across the application.
  • Preloader Adjustments: The frontend preloader logic has been modified, including a temporary disablement and a reduced display duration for debugging and faster development cycles.
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

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 an AI-powered stock analyzer chatbot, a significant new feature. The changes include backend API setup, frontend component integration, and configuration updates. While the feature implementation is largely on track, there are a few important issues to address. In the backend, there's a critical issue in main.py where API routers are registered twice, which will lead to duplicate endpoints. On the frontend, HomeClient.tsx contains leftover debugging code that should be removed, including an unused import. Additionally, the new Chatbot component in layout.tsx is imported using an inconsistent path. Addressing these points will improve the code's correctness and maintainability.

Comment on lines +47 to +51
app.include_router(auth.router, prefix="/api", tags=["Authentication"])
app.include_router(stocks.router, prefix="/api", tags=["Stocks"])
app.include_router(market.router, prefix="/api", tags=["Market"])
app.include_router(portfolios.router, prefix="/api", tags=["Portfolios"])
app.include_router(chatbot.router, prefix="/api", tags=["Chatbot"])
Copy link
Contributor

Choose a reason for hiding this comment

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

high

These routers are being included a second time. They are already included on lines 41-44. This will create duplicate endpoints for auth, stocks, market, and portfolios—one set at the root and another under the /api prefix. Please remove the initial router inclusions on lines 41-44 to resolve this.

"use client";
import { useEffect, useState } from "react";
import Landing from "@/components/Landing";
import SimpleLanding from "@/components/SimpleLanding";
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The SimpleLanding component is imported but is not used within this file. This unused import should be removed to keep the code clean.

Comment on lines +9 to +10
// Temporarily disable preloader for debugging
const [isLoading, setIsLoading] = useState(false);
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 appears to be temporary debugging code that disables the preloader. Please revert this to the original logic before merging.

Suggested change
// Temporarily disable preloader for debugging
const [isLoading, setIsLoading] = useState(false);
const [isLoading, setIsLoading] = useState(!hasShownPreloader);

setIsLoading(false);
hasShownPreloader = true;
}, 2500);
}, 500); // Reduced to 0.5 seconds for testing
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The timeout for the preloader has been reduced for testing purposes. Please revert it to the original value of 2500ms.

Suggested change
}, 500); // Reduced to 0.5 seconds for testing
}, 2500);

import { Toaster as Sonner } from "@/components/ui/sonner";
import { Toaster } from "@/components/ui/toaster";
import { TooltipProvider } from "@/components/ui/tooltip";
import Chatbot from "./components/chatbot";
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 import uses a relative path (./components/chatbot), which is inconsistent with other component imports in this file that use the @/ path alias (e.g., @/components/ui/tooltip on line 5). For consistency and better project structure, it's recommended to place shared components in the top-level components directory and import them using the alias.

Suggested change
import Chatbot from "./components/chatbot";
import Chatbot from "@/components/chatbot";

@Chaitu7032 Chaitu7032 closed this Sep 23, 2025
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.

1 participant