added section for upcoming events

[Ankita-kuntal]

No description provided.

[vercel]

@Ankita-kuntal is attempting to deploy a commit to the Asma's projects Team on Vercel.

A member of the Team first needs to authorize it.

[entelligence-ai-pr-reviews]

🔒 Entelligence AI Vulnerability Scanner

❌ Security analysis failed: Security analysis failed: context deadline exceeded: This error is likely due to exceeding 'timeoutMs' — the total time a long running request (like process or directory watch) can be active. It can be modified by passing 'timeoutMs' when making the request. Use '0' to disable the timeout.

[entelligence-ai-pr-reviews]

correctness: getEventDate returns new Date() (current date) if dates is empty or falsy, causing all such events to be treated as upcoming and possibly misclassified.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Events.jsx, lines 13-20, the `getEventDate` function returns `new Date()` (the current date) if `dates` is empty or falsy. This causes events with missing/empty dates to be misclassified as upcoming. Change the function to return `null` in this case, and ensure all usages of `getEventDate` handle `null` appropriately.

📝 Committable Code Suggestion

‼️ Ensure you review the code suggestion before committing it to the branch. Make sure it replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	const getEventDate = (dates) => {
	if (!dates || dates.length === 0) return new Date();
	// Get the latest date from the dates array for sorting
	const latestDate = dates[dates.length - 1];
	const [day, month, year] = latestDate.split('-');
	return new Date(year, month - 1, day);
	};
	const getEventDate = (dates) => {
	if (!dates || dates.length === 0) return null;
	// Get the latest date from the dates array for sorting
	const latestDate = dates[dates.length - 1];
	const [day, month, year] = latestDate.split('-');
	return new Date(year, month - 1, day);
	};

[entelligence-ai-pr-reviews]

performance: data.events.sort(...) mutates the original array in-place, causing side effects if data.events is reused elsewhere and breaking referential integrity for React state updates.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Events.jsx, lines 41-45, the code mutates the original `data.events` array in-place with `.sort()`, which can cause side effects and break React state update patterns. Refactor to use `[...data.events].sort(...)` to avoid mutating the original array.

📝 Committable Code Suggestion

‼️ Ensure you review the code suggestion before committing it to the branch. Make sure it replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	const sortedEvents = data.events.sort((a, b) => {
	const dateA = getEventDate(a.dates);
	const dateB = getEventDate(b.dates);
	return dateA - dateB;
	});
	const sortedEvents = [...data.events].sort((a, b) => {
	const dateA = getEventDate(a.dates);
	const dateB = getEventDate(b.dates);
	return dateA - dateB;
	});

[entelligence-ai-pr-reviews]

performance: The events are filtered twice for past/upcoming in every useEffect, causing O(n) work twice per render; this can be combined into a single pass for better efficiency on large datasets.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Events.jsx, lines 76-77, the code filters the events array twice to separate past and upcoming events, resulting in two O(n) passes. Refactor to a single loop that pushes each event into either the `upcoming` or `past` array for better performance on large datasets.

📝 Committable Code Suggestion

‼️ Ensure you review the code suggestion before committing it to the branch. Make sure it replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	const upcoming = filtered.filter(event => !isEventPast(event.dates));
	const past = filtered.filter(event => isEventPast(event.dates));
	const upcoming = [];
	const past = [];
	for (const event of filtered) {
	if (isEventPast(event.dates)) {
	past.push(event);
	} else {
	upcoming.push(event);
	}
	}

[entelligence-ai-pr-reviews]

performance: The function getEventDate is called multiple times per event (in sorting, filtering, and rendering), leading to redundant date parsing and computation for each event.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Events.jsx, lines 13-20, 42-43, 76-77, and 319, the function `getEventDate` is called multiple times per event (during sorting, filtering, and rendering), causing redundant date parsing and computation. Optimize by computing and storing the parsed event date once per event (e.g., as a property on the event object) during initial processing, and reuse it throughout the component.

[entelligence-ai-pr-reviews]

performance: The main component function is over 350 lines and contains substantial logic and rendering, making it difficult to maintain and reason about; this is a major maintainability issue.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Events.jsx, lines 1-358, the main Events component is very large and contains substantial logic, state, and rendering, making it hard to maintain. Refactor by extracting major sections (such as filtering logic, event section rendering, and helper functions) into separate components or hooks to improve maintainability and readability.

[entelligence-ai-pr-reviews]

correctness: formatEventDate is referenced in JSX but its definition was deleted, causing a runtime ReferenceError and breaking event date display.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

In client/src/pages/Home.jsx, lines 429-430, the code references `formatEventDate(event.dates)` but the `formatEventDate` function was deleted, causing a runtime ReferenceError and breaking event date display. Restore the date formatting logic inline or as a helper so that event dates render correctly and the app does not crash.

📝 Committable Code Suggestion

‼️ Ensure you review the code suggestion before committing it to the branch. Make sure it replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	{formatEventDate(event.dates)}
	</span>
	<span className="text-sm text-gray-500">
	{(() => {
	if (!event.dates || event.dates.length === 0) return 'Date TBD';
	if (event.dates.length === 1) {
	const [day, month, year] = event.dates[0].split('-');
	const date = new Date(year, month - 1, day);
	return date.toLocaleDateString('en-US', {
	month: 'short',
	day: 'numeric'
	});
	} else {
	const [startDay, startMonth, startYear] = event.dates[0].split('-');
	const [endDay, endMonth, endYear] = event.dates[event.dates.length - 1].split('-');
	const startDate = new Date(startYear, startMonth - 1, startDay);
	const endDate = new Date(endYear, endMonth - 1, endDay);
	return `${startDate.toLocaleDateString('en-US', {
	month: 'short',
	day: 'numeric'
	})} - ${endDate.toLocaleDateString('en-US', {
	month: 'short',
	day: 'numeric'
	})}`;
	}
	})()}

[entelligence-ai-pr-reviews]

performance: The isEventUpcoming and sorting logic in fetchEvents repeatedly parses date strings for every event, leading to O(n) redundant date parsing and object creation on each fetch; this can cause noticeable performance degradation as the number of events grows.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

Optimize date parsing in client/src/pages/Home.jsx lines 82-103. Currently, date strings are parsed multiple times per event during filtering and sorting, causing O(n) redundant computations. Refactor to precompute start and end Date objects for each event before filtering and sorting, so each event's dates are parsed only once. This will significantly improve performance for large event lists.

📝 Committable Code Suggestion

‼️ Ensure you review the code suggestion before committing it to the branch. Make sure it replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	const isEventUpcoming = (dates) => {
	if (!dates || dates.length === 0) return true;
	const latestDate = dates[dates.length - 1];
	const [day, month, year] = latestDate.split('-');
	const eventDate = new Date(year, month - 1, day);
	const today = new Date();
	today.setHours(0, 0, 0, 0);
	return eventDate >= today;
	};
	// Filter for upcoming events and sort by date
	const upcomingEvents = data.events
	.filter(event => isEventUpcoming(event.dates))
	.sort((a, b) => {
	const getDate = (dates) => {
	const [day, month, year] = dates[0].split('-');
	return new Date(year, month - 1, day);
	};
	return getDate(a.dates) - getDate(b.dates);
	})
	// Precompute event dates to avoid repeated parsing
	const today = new Date();
	today.setHours(0, 0, 0, 0);
	const eventsWithParsedDates = data.events.map(event => {
	const startDateParts = event.dates && event.dates[0] ? event.dates[0].split('-') : null;
	const endDateParts = event.dates && event.dates.length > 0 ? event.dates[event.dates.length - 1].split('-') : null;
	return {
	...event,
	startDate: startDateParts ? new Date(startDateParts[2], startDateParts[1] - 1, startDateParts[0]) : null,
	endDate: endDateParts ? new Date(endDateParts[2], endDateParts[1] - 1, endDateParts[0]) : null,
	};
	});
	const upcomingEvents = eventsWithParsedDates
	.filter(event => !event.endDate || event.endDate >= today)
	.sort((a, b) => (a.startDate ? a.startDate - b.startDate : 0))
	.slice(0, 6); // Show only first 6 upcoming events
	setEvents(upcomingEvents);