fix: handle error message case and add workspace info in prompt

Author: bajrangCoder

src/pages/aiAssistant/assistant.js

@@ -237,7 +237,11 @@ export default function openAIAssistantPage() {
 		if (message.role === "user") {
 			messageContent.textContent = message.content;
 		} else {
-			const md = markdownIt();
+			const md = markdownIt({
+				html: true,
+				linkify: true,
+				typographer: true,
+			});
 			messageContent.innerHTML = md.render(message.content);
 		}
 
@@ -680,6 +684,15 @@ export default function openAIAssistantPage() {
 			);
 			if (targetMessageElContent) {
 				targetMessageElContent.innerHTML += errorContent;
+			} else {
+				const assistantErrorMsg = {
+					id: assistantMsgId,
+					conversationId: currentConversationId,
+					role: "assistant",
+					content: errorContent,
+					timestamp: Date.now(),
+				};
+				addMessage(assistantErrorMsg);
 			}
 		} finally {
 			currentController = null;

src/pages/aiAssistant/system_prompt.js

@@ -1,3 +1,5 @@
+import { addedFolder } from "lib/openFolder";
+
 export const SYSTEM_PROMPT = `You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.
 
 ## Communication
@@ -26,4 +28,7 @@ Otherwise, follow debugging best practices:
 1. Unless explicitly requested by the user, use the best suited external APIs and packages to solve the task. There is no need to ask the user for permission.
 2. When selecting which version of an API or package to use, choose one that is compatible with the user's dependency management file(s). If no such file exists or if the package is not present, use the latest version that is in your training data.
 3. If an external API requires an API Key, be sure to point this out to the user. Adhere to best security practices (e.g. DO NOT hardcode an API key in a place where it can be exposed)
+
+SideBar workspace projects(name, absolutePath or url):
+${addedFolder.map((node) => `name: ${node.title}\nurl: ${node.url}`).join("\n")}
 `;