[Bug-Schedule-Builder-Duplicate-Saved-Schedules]: Validate whether a duplicate schedule is being saved

[Castro19]

🐞 Bug Description

When saving a schedule in the Schedule Builder, there is no indication that the schedule has been successfully saved. Additionally, users can save the same schedule multiple times without any restrictions.

✅ Steps to Reproduce

1. Navigate to the Schedule Builder.
2. Create a schedule and save it.
3. Observe that there is no feedback confirming the save action.
4. Attempt to save the same schedule again.
5. Notice that the schedule is saved multiple times without any validation.

🔍 Expected Behavior

• The UI should provide feedback (e.g., a success message or visual indication) when a schedule is saved.
• The system should prevent duplicate schedule saves by checking for existing schedules with the same class numbers.

🖥️ System Information

• OS: [Specify OS]
• Browser: [Specify Browser]
• PolyLink Version: [Specify Version]

📸 Screenshots (If applicable)

Add screenshots if available.

📌 Acceptance Criteria

• ✅ Display a confirmation message or UI feedback when a schedule is saved.
• ✅ Prevent duplicate schedule saves by comparing class numbers.
• ✅ Fix should prevent future occurrences.
• ✅ Should be tested in different environments.

🔧 Technical Notes

• Modify the frontend logic where we dispatch the action to create or update a calendar:
  • [GitHub Permalink](

    LAEP-GPT/Client/src/components/calendar/buildSchedule/CalendarBuilderForm.tsx

    Lines 89 to 96 in 7a529a3

    	const handleSaveSchedule = () => {
    	if (currentCalendar) {
    	dispatch(
    	calendarActions.createOrUpdateCalendarAsync(currentCalendar.sections)
    	);
    	}
    	};

    )
• Update the Redux async thunk that calls the CRUD function for creating/updating calendars:
  • [GitHub Permalink](

    LAEP-GPT/Client/src/redux/calendar/crudCalendar.ts

    Lines 25 to 46 in 7a529a3

    	export async function createOrUpdateCalendar(
    	sections: SelectedSection[]
    	): Promise<{
    	calendars: CalendarListItem[];
    	primaryCalendarId: string;
    	}> {
    	try {
    	const response = await fetch(`${serverUrl}/calendars`, {
    	method: "POST",
    	body: JSON.stringify({ sections }),
    	headers: {
    	"Content-Type": "application/json",
    	},
    	credentials: "include",
    	});
    	const data = await response.json();
    	return data;
    	} catch (error) {
    	console.error("Error creating or updating calendar:", error);
    	throw error;
    	}
    	}

    )
• Implement backend validation in calendarListServices.ts to check for duplicate schedules before inserting:
  • File Path: server/src/db/models/calendar/calendarListServices.ts

📎 Related Issues

• Depends on #XX
• Related to #XX

---

This should help your team track and resolve the issue efficiently! Let me know if you need adjustments. 🚀