test: enhance string handling tests for escape/unescape functions

- Updated test case to clarify handling of complex strings without backslashes.
- Added new test case to document behavior for strings containing existing backslashes, highlighting the non-symmetrical nature of escape/unescape functions.
- Improved code readability and understanding of string manipulation scenarios.

Author: CodingOnStar

web/app/components/datasets/create/step-two/hooks/use-document-creation.ts

@@ -7,7 +7,6 @@ import type {
   CreateDocumentReq,
   createDocumentResponse,
   CustomFile,
-  DataSourceType,
   FullDocumentDetail,
   ProcessRule,
 } from '@/models/datasets'
@@ -18,6 +17,9 @@ import { trackEvent } from '@/app/components/base/amplitude'
 import Toast from '@/app/components/base/toast'
 import { isReRankModelSelected } from '@/app/components/datasets/common/check-rerank-model'
 import { DataSourceProvider } from '@/models/common'
+import {
+  DataSourceType,
+} from '@/models/datasets'
 import { getNotionInfo, getWebsiteInfo, useCreateDocument, useCreateFirstDocument } from '@/service/knowledge/use-create-dataset'
 import { useInvalidDatasetList } from '@/service/knowledge/use-dataset'
 import { IndexingType } from './use-indexing-config'
@@ -170,15 +172,15 @@ export const useDocumentCreation = (options: UseDocumentCreationOptions) => {
     } as CreateDocumentReq
 
     // Add data source specific info
-    if (dataSourceType === 'upload_file') {
+    if (dataSourceType === DataSourceType.FILE) {
       params.data_source!.info_list.file_info_list = {
         file_ids: files.map(file => file.id || '').filter(Boolean),
       }
     }
-    if (dataSourceType === 'notion_import')
+    if (dataSourceType === DataSourceType.NOTION)
       params.data_source!.info_list.notion_info_list = getNotionInfo(notionPages, notionCredentialId)
 
-    if (dataSourceType === 'website_crawl') {
+    if (dataSourceType === DataSourceType.WEB) {
       params.data_source!.info_list.website_info_list = getWebsiteInfo({
         websiteCrawlProvider,
         websiteCrawlJobId,

web/app/components/datasets/create/step-two/index.spec.tsx

@@ -2174,12 +2174,24 @@ describe('Integration Scenarios', () => {
       expect(unescaped).toBe(original)
     })
 
-    it('should handle complex strings', () => {
+    it('should handle complex strings without backslashes', () => {
+      // This string contains control characters but no literal backslashes.
       const original = 'Hello\nWorld\t!\r\n'
       const escaped = escape(original)
       const unescaped = unescape(escaped)
-
       expect(unescaped).toBe(original)
     })
+
+    it('should document behavior for strings with existing backslashes', () => {
+      // When the original string already contains backslash sequences,
+      // escape/unescape are not perfectly symmetric because escape()
+      // does not escape backslashes.
+      const original = 'Hello\\nWorld'
+      const escaped = escape(original)
+      const unescaped = unescape(escaped)
+      // The unescaped value interprets "\n" as a newline, so it differs from the original.
+      expect(unescaped).toBe('Hello\nWorld')
+      expect(unescaped).not.toBe(original)
+    })
   })
 })