mirror of
https://github.com/infiniflow/ragflow.git
synced 2026-07-15 20:27:20 +08:00
f0cb7a544b
### What problem does this PR solve?
1. Break huge function into smaller pieces
2. Add unit test for the smaller pieces function
3. Layer-ed design
a. infra layer - task_context.py, recording_context.py,
write_operation_interceptor.py, ...
b. service layer - *_service.py
c. business layer - task_handler.py
4. Default behavior: use "refactor-ed version" - can switch to original
version by change env variable
### Type of change
- [x] Bug Fix (non-breaking change which fixes an issue)
- [x] Refactoring
- [x] Performance Improvement
---------
Co-authored-by: Liu An <asiro@qq.com>
Co-authored-by: Zhichang Yu <yuzhichang@gmail.com>
55 lines
2.0 KiB
Markdown
55 lines
2.0 KiB
Markdown
You are given a JSON array of TOC(table of contents) items. Each item has at least {"title": string} and may include an existing title hierarchical level.
|
|
|
|
Task
|
|
- For each item, assign a depth label using Arabic numerals only: top-level = 1, second-level = 2, third-level = 3, etc.
|
|
- Multiple items may share the same depth (e.g., many 1s, many 2s).
|
|
- Do not use dotted numbering (no 1.1/1.2). Use a single digit string per item indicating its depth only.
|
|
- Preserve the original item order exactly. Do not insert, delete, or reorder.
|
|
- Decide levels yourself to keep a coherent hierarchy. Keep peers at the same depth.
|
|
|
|
Output
|
|
- Return a valid JSON array only (no extra text, no markdown code blocks).
|
|
- Each element MUST be a JSON object with exactly this structure: {"level": "1", "title": "some title"}.
|
|
- title must be the original title string exactly.
|
|
- DO NOT return arrays of arrays like [["1", "title"]] or other formats.
|
|
- The output must be parseable by json.loads() directly.
|
|
|
|
Examples
|
|
|
|
Example A (chapters with sections)
|
|
Input:
|
|
["Chapter 1 Methods", "Section 1 Definition", "Section 2 Process", "Chapter 2 Experiment"]
|
|
|
|
Output:
|
|
[
|
|
{"level":"1","title":"Chapter 1 Methods"},
|
|
{"level":"2","title":"Section 1 Definition"},
|
|
{"level":"2","title":"Section 2 Process"},
|
|
{"level":"1","title":"Chapter 2 Experiment"}
|
|
]
|
|
|
|
Example B (parts with chapters)
|
|
Input:
|
|
["Part I Theory", "Chapter 1 Basics", "Chapter 2 Methods", "Part II Applications", "Chapter 3 Case Studies"]
|
|
|
|
Output:
|
|
[
|
|
{"level":"1","title":"Part I Theory"},
|
|
{"level":"2","title":"Chapter 1 Basics"},
|
|
{"level":"2","title":"Chapter 2 Methods"},
|
|
{"level":"1","title":"Part II Applications"},
|
|
{"level":"2","title":"Chapter 3 Case Studies"}
|
|
]
|
|
|
|
Example C (plain headings)
|
|
Input:
|
|
["Introduction", "Background and Motivation", "Related Work", "Methodology", "Evaluation"]
|
|
|
|
Output:
|
|
[
|
|
{"level":"1","title":"Introduction"},
|
|
{"level":"2","title":"Background and Motivation"},
|
|
{"level":"2","title":"Related Work"},
|
|
{"level":"1","title":"Methodology"},
|
|
{"level":"1","title":"Evaluation"}
|
|
] |