Release of v0.0.3 #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



[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