Skip to content

fix: Fix duplicate Calendar import in CustomerDashboard#381

Open
sanikayadav2024 wants to merge 1 commit into
anubhavxdev:mainfrom
sanikayadav2024:fix-error-customer-dashboard
Open

fix: Fix duplicate Calendar import in CustomerDashboard#381
sanikayadav2024 wants to merge 1 commit into
anubhavxdev:mainfrom
sanikayadav2024:fix-error-customer-dashboard

Conversation

@sanikayadav2024
Copy link
Copy Markdown

@sanikayadav2024 sanikayadav2024 commented Jun 3, 2026

Description

The file CustomerDashboard.jsx has number of errors stopping the application from running , as it givig so many logs on page after starting application. This PR fixes all errors in the jsx page which blocking the application run. Closes #380

Changes Made

  • Fixed the reported issue.
  • Updated the code.
  • Ensured consistency of code.
  • Removed duplicate code statements causing errors.

Type of Change

  • Bug Fix
  • New Feature
  • Documentation Update
  • Refactoring

Screenshots

Before fixing bugs application is not running on browser and throeing these errors

Screenshot 2026-06-02 210150

After Bug Fixing : Application run as Expected

image

Testing

  • Tested locally in the development environment.
  • Verified that the issue is resolved.
  • Confirmed that no existing functionality was affected.

Additional informathion

This contribution is under GSSoC'26

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 3, 2026

@sanikayadav2024 is attempting to deploy a commit to the anubhav12302387's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 3, 2026

❌ PR Format Check — Failed — Please Fix Below

Hi @sanikayadav2024! Please fix the issues below before your PR can proceed to mentor review.

❌ Must Fix Before Proceeding

Issue #380 is not assigned to you (@sanikayadav2024) — You must be assigned to the issue before submitting a PR.

Comment /assign on Issue #380 or ask a maintainer to assign it to you.


📋 EventOne PR Guidelines (click to expand)

Title format — Conventional Commits:
feat: · fix: · docs: · style: · refactor: · test: · chore: · perf:

Always link an issue: Closes #number

Use a feature branch — never PR directly from main

Write your own description — AI-generated content = gssoc:ai-slop label

EventOne × GSSoC Pipeline — Stage 1 Automated Check

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 3, 2026

👋 Thanks for opening a PR, @sanikayadav2024!

Your PR has entered the 🎯 EventOne GSSoC PR Review Pipeline.

🟢 GSSoC PR detected — your PR will be routed to an approved GSSoC mentor for Stage 2 review.

What happens next

Stage Reviewer Checks
Stage 1 — Automated Validation 🤖 Bot Title format · Issue link · AI Slop · Branch check
Stage 2 — Mentor Review 🧑‍🏫 GSSoC Mentor Code + Quality Review
Stage 3 — Admin Final Gate 🔑 @anubhavxdev Label check + Final Merge Decision

A pipeline status comment will appear below and update automatically as your PR progresses.


While you wait

  • Sign all commits using git commit -s
  • Link your issue with Closes #123
  • Use a feature branch — not main
  • Avoid unrelated changes in the same PR
  • Write your own description — no AI-generated content

This comment is posted only once.

EventOne × GSSoC Automated Pipeline

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.

[BUG] Failure of starting Application (Critical bug)

1 participant