"Edit Fix" codes for sahar's inspection by yaad96 · Pull Request #74 · devuxd/active-doc-client

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.

yaad96 · 2024-07-29T19:48:04Z

No description provided.

2. used GPT-5.2 3. fixed the bug where texts were overflowing out of the textboxes.

…tion from frontend to extension and then to vscode workspace's "untitled" file

… sections Previously, surroundingNodes was passed as the violation parameter, mislabeling it in the LLM prompt. Now the actual violation snippet and surrounding class/method context are passed as separate, explicitly labeled sections (<<<VIOLATION_SNIPPET>>> and <<<SURROUNDING_CONTEXT>>>), enabling the LLM to distinguish what to fix from what to reference.