Releases: SafetyCulture/safetyculture-exporter-ui
v1.19.4
v1.19.3
What's Changed
Full Changelog: v1.19.2...v1.19.3
Contributors
Assets 5
v1.19.2
What's Changed
- [INTG-1601]: Bump the dependencies group with 2 updates by @dependabot in #121
- INTG-3379 - bump up the exporter cli version (4.18.2) by @sc-gv in #122
Full Changelog: v1.19.1...v1.19.2
Contributors
Assets 5
v1.19.1
What's Changed
- Update Icon by @BCook98 in #118
- [INTG-1601]: Bump github.com/wailsapp/wails/v2 from 2.8.0 to 2.8.1 in the dependencies group by @dependabot in #119
- INTG-3206 - windows code signing cert renewal by @sc-gv in #120
New Contributors
Full Changelog: v1.19.0...v1.19.1
Contributors
Assets 5
v1.19.0
v1.18.0
v1.17.0
What's Changed
- asset ID for schedules feed by @MickStanciu in #114
Full Changelog: v1.16.1...v1.17.0
Contributors
Assets 5
v1.16.1
This release fixes a bug that re-checked the ApiKey on application startup
What's Changed
- INTG-3224 fix api key validation by @MickStanciu in #113
Full Changelog: v1.16.0...v1.16.1
Contributors
Assets 5
v1.16.0
This release enables an experimental flag
schedule:
resume_download: true
The feed schedule_occurrences doesn’t have a natural way to resume a download. So I am using the field start_time to detect the last record downloaded and exported.
That means: If the customer sets export from 01-Jan-2024 and downloads the whole schedules, and next day the customer runs again … the new feature flag resume_download: true will look in the database for the latest record where the start_time is the most current and will resume from there.
Caveat:
If the customer creates new schedules IN THE PAST, these of course would not be seen, unless they have occurrences in the future.
So the trade off is: maybe some old data will be skipped, but new data is always appended.
Of course, this doesn’t stop the customer to put the flag back to false, to a full download, then change it back.