github/node-DeepResearch
1
0
Fork 0
mirror of https://github.com/jina-ai/node-DeepResearch.git synced 2025-12-26 06:28:56 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: md table render

Browse Source
This commit is contained in:
Han Xiao 2025-03-20 15:13:39 +08:00
parent d748febafc
commit c299a3a4bb
2 changed files with 9 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/tools/evaluator.ts
View File

@ -22,7 +22,7 @@ Markdown or JSON formatting issue is never your concern and should never be ment
You always endorse answers in most readable natural language format.
If multiple sections have very similar structure, suggest another presentation format like a table to make the content more readable.
Do not encourage deeply nested structure, flatten it into natural language sections/paragraphs or even tables. Every table should always follow HTML table syntax <table> <thead> <tr> <th> <td> without any CSS styling.
Do not encourage deeply nested structure, flatten it into natural language sections/paragraphs or even tables. Every table should use HTML table syntax <table> <thead> <tr> <th> <td> without any CSS styling.
The following knowledge items are provided for your reference. Note that some of them may not be directly related to the question/answer user provided, but may give some subtle hints and insights:
${KnowledgeStr.join('\n\n')}

17
src/tools/md-fixer.ts
View File

@ -16,15 +16,14 @@ Your task is to repair the provided markdown content while preserving its origin
<rules>
1. Fix any broken tables, lists, code blocks, footnotes, or formatting issues. Tables must always in basic HTML table syntax with proper <table> <thead> <tr> <th> <td> without any CSS styling. STRICTLY AVOID any markdown table syntax.
2. Make sure code blocks are properly closed and languages are correctly specified.
3. Make sure nested lists are correctly indented, especially code blocks within the nested structure.
4. Use available knowledge to restore incomplete content.
5. Flatten deeply nested structure into natural language sections/paragraphs to make the content more readable.
6. In the footnote section, keep each footnote items format and repair misaligned and duplicated footnotes. Each footnote item must contain a URL at the end.
7. In the actual content, to cite multiple footnotes in a row use [^1][^2][^3], never [^1,2,3] or [^1-3].
8. Pay attention to the original content's ending (before the footnotes section). If you find a very obvious incomplete/broken/interrupted ending, continue the content with a proper ending.
9. Repair any <EFBFBD><EFBFBD> symbols or other broken characters in the original content by decoding them to the correct content.
10. Replace any obvious placeholders or Lorem Ipsum values such as "example.com" with the actual content derived from the knowledge.
2. Make sure nested lists are correctly indented, especially code blocks within the nested structure.
3. Use available knowledge to restore incomplete content.
4. Flatten deeply nested structure into natural language sections/paragraphs to make the content more readable.
5. In the footnote section, keep each footnote items format and repair misaligned and duplicated footnotes. Each footnote item must contain a URL at the end.
6. In the actual content, to cite multiple footnotes in a row use [^1][^2][^3], never [^1,2,3] or [^1-3].
7. Pay attention to the original content's ending (before the footnotes section). If you find a very obvious incomplete/broken/interrupted ending, continue the content with a proper ending.
8. Repair any <EFBFBD><EFBFBD> symbols or other broken characters in the original content by decoding them to the correct content.
9. Replace any obvious placeholders or Lorem Ipsum values such as "example.com" with the actual content derived from the knowledge.
</rules>
The following knowledge items are provided for your reference. Note that some of them may not be directly related to the content user provided, but may give some subtle hints and insights: