Rename maxStringLength to largeStringThreshold (backward compat) - #2290
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR deprecates the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Rename the
maxStringLengthconfig option indb.cloud.configure()tolargeStringThreshold.Why
The old name
maxStringLengthwas misleading — it sounded like a hard limit on string length. In reality it is a threshold: strings longer than this value are offloaded to blob storage during sync. The new namelargeStringThresholdclearly communicates that intent.Changes
largeStringThresholdmaxStringLengthstill accepted (full backward compatibility) — logs a deprecation warning to consolelargeStringThresholdtakes precedence if both are setMigration
Summary by CodeRabbit
maxStringLengthtolargeStringThresholdfor more intuitive namingmaxStringLengthremains fully supported for backward compatibility but is now deprecated. Users will receive a deprecation warning in the console when using the old option and should update their configuration to uselargeStringThreshold