deps: bump decimal to 3.1#92
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughWalEx centralizes Decimal parsing options via a module attribute and applies unbounded-precision options across numeric, money, and array casting paths. The :decimal dependency is upgraded to ~> 3.1 with override: true. ChangesDecimal Arbitrary-Precision Support
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Actionable comments posted: 0 |
Decimal v3 applies decimal128 parse limits (34 digits, exp ±6144) via Decimal.new/1, which raises on large Postgres numeric values. Parse with max_digits/max_exponent: :infinity to keep arbitrary-precision casting. Pulls postgrex 0.22.2, whose constraint allows decimal ~> 3.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Actionable comments posted: 0 |
Decimal v3 applies decimal128 parse limits (34 digits, exp ±6144) via Decimal.new/1, which raises on large Postgres numeric values. Parse with max_digits/max_exponent: :infinity to keep arbitrary-precision casting.
Pulls postgrex 0.22.2, whose constraint allows decimal ~> 3.0.
Summary by CodeRabbit
Improvements
Chores