Kl/scrum 148 chatbot fixes (#102)

Co-authored-by: kevin-lann <[email protected]>

Author: kevin-lann

course-matrix/backend/package-lock.json

@@ -247,14 +247,20 @@ export const chat = asyncHandler(async (req: Request, res: Response) => {
             - Include course codes when referencing specific courses
             - If information is missing from the context but likely exists, try to use info from web to answer. If still not able to form a decent response, acknowledge the limitation
             - For unrelated questions, politely explain that you're specialized in UTSC academic information
-            - Format long lists of timetables as a table
+            - Format long lists of timetables as a table 
 
             ## Tool call guidelines
             - Include the timetable ID in all getTimetables tool call responses
             - Link: For every tool call, for each timetable that it gets/deletes/modifies/creates, include a link with it displayed as "View Timetable" to ${process.env.CLIENT_APP_URL}/dashboard/timetable?edit=[[TIMETABLE_ID]] , where TIMETABLE_ID is the id of the respective timetable.
             - If the user provides a course code of length 6 like CSCA08, then assume they mean CSCA08H3 (H3 appended)
             - If the user wants to create a timetable, first call getCourses to get course information on the requested courses, then call generateTimetable.
             - Do not make up fake courses or offerings. 
+            - For delete timetable requests, if the user asks to delete an ambiguous timetable name (i.e many with similar name exist) then ask them to clarify which one
+            - For delete timetable requests, first check that the timetable the user is refering to exists 
+            - For delete timetable requests, ask for user confirmation with command "/timetable confirm" before proceeding. If their next message is anything other than "/timetable confim" then cancel the deletion. 
+            - After a deletion has been cancelled, /timetable confirm will do nothing. If the user wants to delete again after cancelling, they must specify so.
+            - Do not create multiple timetables for a single user query. Each user query can create at most 1 timetable
+            - If you try to update or create a timetable but you get an error saying a timetable with the same name already exists, then ask the user to rename
             `,
         messages,
         tools: {
@@ -293,7 +299,7 @@ export const chat = asyncHandler(async (req: Request, res: Response) => {
               "Return a list of possible timetables based on provided courses and restrictions.",
             parameters: TimetableFormSchema,
             execute: async (args) => {
-              // console.log("Args for generate: ", args)
+              console.log("Args for generate: ", args);
               console.log("restrictions :", JSON.stringify(args.restrictions));
               const data = await availableFunctions.generateTimetable(
                 args,

course-matrix/backend/src/controllers/aiController.ts

@@ -48,7 +48,7 @@ const ThreadListItem: FC = () => {
 
 const ThreadListItemTitle: FC = () => {
   return (
-    <p className="text-sm overflow-hidden text-ellipsis whitespace-nowrap max-w-[150px]">
+    <p className="text-sm overflow-hidden text-ellipsis max-w-[150px]">
       <ThreadListItemPrimitive.Title fallback="New Chat" />
     </p>
   );