Conversation
fix(daily-closure)!: align DailyClosure type with actual API response BREAKING CHANGE: DailyClosure type now matches real API with shop_daily_closure and device_daily_closure objects. Removed incorrect payments_count field. Added Date object support to get() method.
Daily Closure
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|



[0.0.3] - 2025-12-03
Changed
DailyClosuretype structure completely rewritten to match actual Satispay API responseshop_daily_closureanddevice_daily_closureobjectsid,type,customer_uid,gross_amount_unit,refund_amount_unit,amount_unit,currencyDailyClosuretype:datefield (useshop_daily_closure.idinstead)total_amount_unitfield (useshop_daily_closure.amount_unitinstead)payments_countfield (not provided by Satispay API)DailyClosure.get()now acceptsDateobjects in addition to string dates (YYYYMMDD format)Dateobject usage examplesAdded
DailyClosureDetailtype for structured closure informationDateUtils.formatToYYYYMMDD()utility function for date formattingDateobject support inDailyClosure.get()Fixed
DailyClosuretype now accurately reflects Satispay's actual API response