files-com 1.6.51__tar.gz → 1.6.52__tar.gz

{files_com-1.6.51/files_com.egg-info → files_com-1.6.52}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: files_com
-Version: 1.6.51
+Version: 1.6.52
 Summary: Python bindings for the Files.com API
 License: MIT
 Requires-Python: >=3.5
@@ -374,6 +374,73 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
+## Paths
+
+Working with paths in Files.com involves several important considerations. Understanding how path comparisons are applied helps developers ensure consistency and accuracy across all interactions with the platform.
+<div></div>
+
+### Capitalization
+
+Files.com compares paths in a **case-insensitive** manner. This means path segments are treated as equivalent regardless of letter casing.
+
+For example, all of the following resolve to the same internal path:
+
+| Path Variant                          | Interpreted As              |
+|---------------------------------------|------------------------------|
+| `Documents/Reports/Q1.pdf`            | `documents/reports/q1.pdf`  |
+| `documents/reports/q1.PDF`            | `documents/reports/q1.pdf`  |
+| `DOCUMENTS/REPORTS/Q1.PDF`            | `documents/reports/q1.pdf`  |
+
+This behavior applies across:
+- API requests
+- Folder and file lookup operations
+- Automations and workflows
+
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+
+The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
+your native file system would be considered the same on Files.com. This is particularly important
+when handling errors related to duplicate file names and when developing tools for folder
+synchronization.
+
+```python title="Compare Case-Insensitive Files and Paths"
+import files_sdk
+
+if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
+    print("Paths are the same")
+```
+
+### Slashes
+
+All path parameters in Files.com (API, SDKs, CLI, automations, integrations) must **omit leading and trailing slashes**. Paths are always treated as **absolute and slash-delimited**, so only internal `/` separators are used and never at the start or end of the string.
+
+####  Path Slash Examples
+| Path                              | Valid? | Notes                         |
+|-----------------------------------|--------|-------------------------------|
+| `folder/subfolder/file.txt`       |   ✅   | Correct, internal separators only |
+| `/folder/subfolder/file.txt`      |   ❌   | Leading slash not allowed     |
+| `folder/subfolder/file.txt/`      |   ❌   | Trailing slash not allowed    |
+| `//folder//file.txt`              |   ❌   | Duplicate separators not allowed |
+
+<div></div>
+
+### Unicode Normalization
+
+Files.com normalizes all paths using [Unicode NFC (Normalization Form C)](https://www.unicode.org/reports/tr15/#Norm_Forms) before comparison. This ensures consistency across different representations of the same characters.
+
+For example, the following two paths are treated as equivalent after NFC normalization:
+
+| Input                                  | Normalized Form       |
+|----------------------------------------|------------------------|
+| `uploads/\u0065\u0301.txt`             | `uploads/é.txt`        |
+| `docs/Café/Report.txt`                 | `docs/Café/Report.txt` |
+
+- All input must be UTF‑8 encoded.
+- Precomposed and decomposed characters are unified.
+- This affects search, deduplication, and comparisons across SDKs.
+
+<div></div>
+
 ## Foreign Language Support
 
 The Files.com Python SDK supports localized responses by using the `files_sdk.set_language` configuration method.
@@ -671,22 +738,6 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
-## Case Sensitivity
-
-The Files.com API compares files and paths in a case-insensitive manner. For related documentation see [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity).
-
-The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
-your native file system would be considered the same on Files.com. This is particularly important
-when handling errors related to duplicate file names and when developing tools for folder
-synchronization.
-
-```python title="Compare Case-Insensitive Files and Paths"
-import files_sdk
-
-if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
-    print("Paths are the same")
-```
-
 ## Mock Server
 
 Files.com publishes a Files.com API server, which is useful for testing your use of the Files.com

{files_com-1.6.51 → files_com-1.6.52}/README.md

@@ -362,6 +362,73 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
+## Paths
+
+Working with paths in Files.com involves several important considerations. Understanding how path comparisons are applied helps developers ensure consistency and accuracy across all interactions with the platform.
+<div></div>
+
+### Capitalization
+
+Files.com compares paths in a **case-insensitive** manner. This means path segments are treated as equivalent regardless of letter casing.
+
+For example, all of the following resolve to the same internal path:
+
+| Path Variant                          | Interpreted As              |
+|---------------------------------------|------------------------------|
+| `Documents/Reports/Q1.pdf`            | `documents/reports/q1.pdf`  |
+| `documents/reports/q1.PDF`            | `documents/reports/q1.pdf`  |
+| `DOCUMENTS/REPORTS/Q1.PDF`            | `documents/reports/q1.pdf`  |
+
+This behavior applies across:
+- API requests
+- Folder and file lookup operations
+- Automations and workflows
+
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+
+The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
+your native file system would be considered the same on Files.com. This is particularly important
+when handling errors related to duplicate file names and when developing tools for folder
+synchronization.
+
+```python title="Compare Case-Insensitive Files and Paths"
+import files_sdk
+
+if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
+    print("Paths are the same")
+```
+
+### Slashes
+
+All path parameters in Files.com (API, SDKs, CLI, automations, integrations) must **omit leading and trailing slashes**. Paths are always treated as **absolute and slash-delimited**, so only internal `/` separators are used and never at the start or end of the string.
+
+####  Path Slash Examples
+| Path                              | Valid? | Notes                         |
+|-----------------------------------|--------|-------------------------------|
+| `folder/subfolder/file.txt`       |   ✅   | Correct, internal separators only |
+| `/folder/subfolder/file.txt`      |   ❌   | Leading slash not allowed     |
+| `folder/subfolder/file.txt/`      |   ❌   | Trailing slash not allowed    |
+| `//folder//file.txt`              |   ❌   | Duplicate separators not allowed |
+
+<div></div>
+
+### Unicode Normalization
+
+Files.com normalizes all paths using [Unicode NFC (Normalization Form C)](https://www.unicode.org/reports/tr15/#Norm_Forms) before comparison. This ensures consistency across different representations of the same characters.
+
+For example, the following two paths are treated as equivalent after NFC normalization:
+
+| Input                                  | Normalized Form       |
+|----------------------------------------|------------------------|
+| `uploads/\u0065\u0301.txt`             | `uploads/é.txt`        |
+| `docs/Café/Report.txt`                 | `docs/Café/Report.txt` |
+
+- All input must be UTF‑8 encoded.
+- Precomposed and decomposed characters are unified.
+- This affects search, deduplication, and comparisons across SDKs.
+
+<div></div>
+
 ## Foreign Language Support
 
 The Files.com Python SDK supports localized responses by using the `files_sdk.set_language` configuration method.
@@ -659,22 +726,6 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
-## Case Sensitivity
-
-The Files.com API compares files and paths in a case-insensitive manner. For related documentation see [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity).
-
-The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
-your native file system would be considered the same on Files.com. This is particularly important
-when handling errors related to duplicate file names and when developing tools for folder
-synchronization.
-
-```python title="Compare Case-Insensitive Files and Paths"
-import files_sdk
-
-if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
-    print("Paths are the same")
-```
-
 ## Mock Server
 
 Files.com publishes a Files.com API server, which is useful for testing your use of the Files.com

files_com-1.6.52/_VERSION

@@ -0,0 +1 @@
+1.6.52

{files_com-1.6.51 → files_com-1.6.52/files_com.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: files_com
-Version: 1.6.51
+Version: 1.6.52
 Summary: Python bindings for the Files.com API
 License: MIT
 Requires-Python: >=3.5
@@ -374,6 +374,73 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
+## Paths
+
+Working with paths in Files.com involves several important considerations. Understanding how path comparisons are applied helps developers ensure consistency and accuracy across all interactions with the platform.
+<div></div>
+
+### Capitalization
+
+Files.com compares paths in a **case-insensitive** manner. This means path segments are treated as equivalent regardless of letter casing.
+
+For example, all of the following resolve to the same internal path:
+
+| Path Variant                          | Interpreted As              |
+|---------------------------------------|------------------------------|
+| `Documents/Reports/Q1.pdf`            | `documents/reports/q1.pdf`  |
+| `documents/reports/q1.PDF`            | `documents/reports/q1.pdf`  |
+| `DOCUMENTS/REPORTS/Q1.PDF`            | `documents/reports/q1.pdf`  |
+
+This behavior applies across:
+- API requests
+- Folder and file lookup operations
+- Automations and workflows
+
+See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
+
+The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
+your native file system would be considered the same on Files.com. This is particularly important
+when handling errors related to duplicate file names and when developing tools for folder
+synchronization.
+
+```python title="Compare Case-Insensitive Files and Paths"
+import files_sdk
+
+if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
+    print("Paths are the same")
+```
+
+### Slashes
+
+All path parameters in Files.com (API, SDKs, CLI, automations, integrations) must **omit leading and trailing slashes**. Paths are always treated as **absolute and slash-delimited**, so only internal `/` separators are used and never at the start or end of the string.
+
+####  Path Slash Examples
+| Path                              | Valid? | Notes                         |
+|-----------------------------------|--------|-------------------------------|
+| `folder/subfolder/file.txt`       |   ✅   | Correct, internal separators only |
+| `/folder/subfolder/file.txt`      |   ❌   | Leading slash not allowed     |
+| `folder/subfolder/file.txt/`      |   ❌   | Trailing slash not allowed    |
+| `//folder//file.txt`              |   ❌   | Duplicate separators not allowed |
+
+<div></div>
+
+### Unicode Normalization
+
+Files.com normalizes all paths using [Unicode NFC (Normalization Form C)](https://www.unicode.org/reports/tr15/#Norm_Forms) before comparison. This ensures consistency across different representations of the same characters.
+
+For example, the following two paths are treated as equivalent after NFC normalization:
+
+| Input                                  | Normalized Form       |
+|----------------------------------------|------------------------|
+| `uploads/\u0065\u0301.txt`             | `uploads/é.txt`        |
+| `docs/Café/Report.txt`                 | `docs/Café/Report.txt` |
+
+- All input must be UTF‑8 encoded.
+- Precomposed and decomposed characters are unified.
+- This affects search, deduplication, and comparisons across SDKs.
+
+<div></div>
+
 ## Foreign Language Support
 
 The Files.com Python SDK supports localized responses by using the `files_sdk.set_language` configuration method.
@@ -671,22 +738,6 @@ except files_sdk.error.Error as err:
   print(f"Unknown Error Occurred ({type(err).__name__}):", err)
 ```
 
-## Case Sensitivity
-
-The Files.com API compares files and paths in a case-insensitive manner. For related documentation see [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/file-system-semantics/case-sensitivity).
-
-The `path_util.is_same` function in the Files.com SDK is designed to help you determine if two paths on
-your native file system would be considered the same on Files.com. This is particularly important
-when handling errors related to duplicate file names and when developing tools for folder
-synchronization.
-
-```python title="Compare Case-Insensitive Files and Paths"
-import files_sdk
-
-if files_sdk.path_util.is_same("Fïłèńämê.Txt", "filename.txt"):
-    print("Paths are the same")
-```
-
 ## Mock Server
 
 Files.com publishes a Files.com API server, which is useful for testing your use of the Files.com

{files_com-1.6.51 → files_com-1.6.52}/files_sdk/__init__.py

@@ -227,7 +227,7 @@ session_id = None
 source_ip = None
 base_url = "https://app.files.com"
 base_path = "api/rest/v1"
-version = "1.6.51"
+version = "1.6.52"
 
 __version__ = version
 

{files_com-1.6.51 → files_com-1.6.52}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "files_com"
-version = "1.6.51"
+version = "1.6.52"
 description = "Python bindings for the Files.com API"
 readme = "README.md"
 license = { text = "MIT" }

files_com-1.6.51/_VERSION

@@ -1 +0,0 @@
-1.6.51