Export History writes a tag's whole stored history. There is no way to export just a range.
This is bounded in practice — the app only holds what it has fetched — and the CSV carries
timestamp_utc, timestamp_local and timestamp_epoch_ms, so filtering afterwards in a
spreadsheet is a column sort. But somebody with months of history who wants one weekend has to
export all of it.
If it is worth doing, the natural place is a date-range picker between the selection bar and
the storage picker, defaulting to everything. The history page is already day-scoped, so the
range concept exists in the UI. BeaconRepository.getLocationsFor already takes a start and
end, and the export currently passes 0 and Long.MAX_VALUE.
Deliberately left out of the export change to keep that one small, and because "all of it" is
what most people exporting a tag's history will want anyway.
This issue was written by Claude Code.
Export History writes a tag's whole stored history. There is no way to export just a range.
This is bounded in practice — the app only holds what it has fetched — and the CSV carries
timestamp_utc,timestamp_localandtimestamp_epoch_ms, so filtering afterwards in aspreadsheet is a column sort. But somebody with months of history who wants one weekend has to
export all of it.
If it is worth doing, the natural place is a date-range picker between the selection bar and
the storage picker, defaulting to everything. The history page is already day-scoped, so the
range concept exists in the UI.
BeaconRepository.getLocationsForalready takes a start andend, and the export currently passes
0andLong.MAX_VALUE.Deliberately left out of the export change to keep that one small, and because "all of it" is
what most people exporting a tag's history will want anyway.
This issue was written by Claude Code.