files.com 1.1.309 → 1.1.310

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a4ba4caf21009c3188cf188a280d1f76adec2660ef522e47fb906d54d205ad8c
4
- data.tar.gz: c4d36691238441dc50f125d296ca955217a3ef6824def876465f1b259c78f847
3
+ metadata.gz: 6ce1185b83e43ac2f0ed150a9a155b9b185a5c507a336662d68ea32474163693
4
+ data.tar.gz: 1b6381d8c2a4fbbaec22c4a59272028716cfe2a5457126a60d2f86a5ba2e2ac0
5
5
  SHA512:
6
- metadata.gz: 8d8e630bcdbb2ff30f14f06d86176aa41863305c20d2011d151b86663fb98ffea8ceb07e935fd39a7d7abc0ec2b912fafc767337597cec18bc8ef0b97493063f
7
- data.tar.gz: 5c22b138cac4106b3da4078ecb7d4eef19a933d2cbe61eb345ce49c7168687eb75ffbf9f89c2e9528f5114665051198e5929730663a347900a236d2ed14c7dd3
6
+ metadata.gz: 67e3746e74cec4bccfb809c4a266f942ba02ee0182d316913acf9a43b7a77d5afa9eb1de19c40bdbbeab6f5f3fa43117406a82c88f814ad666c55b8b6e64fc9a
7
+ data.tar.gz: 3dd482ab685b322663c2b28a2ee657c65431537e77dc4d9c0255a1d92fc341cdc7bac6b31e61968eeb9902e8bf0b668921d24b7e0717431206b6fd8cf52e2323
data/README.md CHANGED
@@ -335,6 +335,61 @@ rescue Files::Error => e
335
335
  end
336
336
  ```
337
337
 
338
+ ## Paths
339
+
340
+ 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.
341
+ <div></div>
342
+
343
+ ### Capitalization
344
+
345
+ Files.com compares paths in a **case-insensitive** manner. This means path segments are treated as equivalent regardless of letter casing.
346
+
347
+ For example, all of the following resolve to the same internal path:
348
+
349
+ | Path Variant | Interpreted As |
350
+ |---------------------------------------|------------------------------|
351
+ | `Documents/Reports/Q1.pdf` | `documents/reports/q1.pdf` |
352
+ | `documents/reports/q1.PDF` | `documents/reports/q1.pdf` |
353
+ | `DOCUMENTS/REPORTS/Q1.PDF` | `documents/reports/q1.pdf` |
354
+
355
+ This behavior applies across:
356
+ - API requests
357
+ - Folder and file lookup operations
358
+ - Automations and workflows
359
+
360
+ See also: [Case Sensitivity Documentation](https://www.files.com/docs/files-and-folders/case-sensitivity/)
361
+
362
+ ### Slashes
363
+
364
+ 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.
365
+
366
+ #### Path Slash Examples
367
+ | Path | Valid? | Notes |
368
+ |-----------------------------------|--------|-------------------------------|
369
+ | `folder/subfolder/file.txt` | ✅ | Correct, internal separators only |
370
+ | `/folder/subfolder/file.txt` | ❌ | Leading slash not allowed |
371
+ | `folder/subfolder/file.txt/` | ❌ | Trailing slash not allowed |
372
+ | `//folder//file.txt` | ❌ | Duplicate separators not allowed |
373
+
374
+ <div></div>
375
+
376
+ ### Unicode Normalization
377
+
378
+ 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.
379
+
380
+ For example, the following two paths are treated as equivalent after NFC normalization:
381
+
382
+ | Input | Normalized Form |
383
+ |----------------------------------------|------------------------|
384
+ | `uploads/\u0065\u0301.txt` | `uploads/é.txt` |
385
+ | `docs/Café/Report.txt` | `docs/Café/Report.txt` |
386
+
387
+ - All input must be UTF‑8 encoded.
388
+ - Precomposed and decomposed characters are unified.
389
+ - This affects search, deduplication, and comparisons across SDKs.
390
+
391
+ <div></div>
392
+
338
393
  ## Foreign Language Support
339
394
 
340
395
  The Files.com Ruby SDK supports localized responses by using the `Files.language` configuration attribute.
@@ -609,10 +664,6 @@ rescue Files::Error => e
609
664
  end
610
665
  ```
611
666
 
612
- ## Case Sensitivity
613
-
614
- 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).
615
-
616
667
  ## Mock Server
617
668
 
618
669
  Files.com publishes a Files.com API server, which is useful for testing your use of the Files.com
data/_VERSION CHANGED
@@ -1 +1 @@
1
- 1.1.309
1
+ 1.1.310
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Files
4
- VERSION = "1.1.309"
4
+ VERSION = "1.1.310"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: files.com
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.309
4
+ version: 1.1.310
5
5
  platform: ruby
6
6
  authors:
7
7
  - files.com