mirror of
https://github.com/langgenius/dify.git
synced 2026-09-05 08:48:10 +08:00
| .. | ||
| __tests__ | ||
| components | ||
| create | ||
| documents | ||
| list | ||
| overview | ||
| quality | ||
| retrieval | ||
| settings | ||
| sources | ||
| space | ||
| upgrade | ||
| upload | ||
| constants.ts | ||
| knowledge-fs-task-error.ts | ||
| README.md | ||
| request-id.ts | ||
| routes.ts | ||
| use-knowledge-model-setup-guard.ts | ||
New RAG
This feature owns the KnowledgeFS-backed knowledge list, creation flows, sources, documents, revisions, retrieval evaluation, and processing tasks.
- Route surfaces live in
create/,documents/,sources/,retrieval/,quality/,settings/,space/, andoverview/; feature tests stay beside their owning surface. list/owns the KnowledgeFS list integration used by the existing dataset list, whileupload/owns upload behavior shared by creation and document-management flows.routes.tsowns navigation only; shared source drafts, provider discovery, datasource parameters, and setup fields belong tosources/setup/.create/,sources/create/, and source editing own their distinct submission lifecycles; setup modules do not submit those workflows.sources/connections/owns provider identity matching and connection ranking across source flows.documents/owns document list and detail behavior, query options, permission recovery, task recovery, and metadata editing.- Shared KnowledgeFS read contracts used by other features live under
service/knowledge-fs/; feature-specific editing policy remains here. - Document query modules own server-state configuration. View components consume those options and coordinate only workflows that require one consistent page snapshot.
- Document processing events live with
documents/tasks/; retrieval event streams live withretrieval/services/. - Creation and processing overlays are feature compositions of Dify UI Dialog, AlertDialog, Drawer, and Popover primitives.
Files in this directory remain feature-owned; direct consumers do not become their owners. Keep shared dataset APIs and permission policy in their existing owners rather than copying them into this feature.