jubnl 70459dc085 fix(journey): make sort_order authoritative for within-day entry ordering ...

Reorder buttons appeared broken because the server ORDER BY put entry_time
before sort_order, so entries synced from trip places with differing times
would always sort by time regardless of sort_order writes. The client store
mirrored the same comparator, making even the optimistic update invisible.

- Change ORDER BY to (entry_date, sort_order, id) in getJourneyFull and listEntries
- Fix syncTripPlaces and onPlaceCreated to assign MAX+1 sort_order per day instead of day_number/0
- Update client store comparator to match
- Add DB migration to backfill sort_order using old effective key (entry_time, id) so existing journeys retain their visual order
- Add tests: JOURNEY-SVC-089–093, FE-STORE-JOURNEY-018–019

Closes #846

2026-04-23 10:28:21 +02:00

..

fixtures

feat(import): selective GPX/KML element import and performance improvements

2026-04-18 01:28:37 +02:00

helpers

feat(notices): add system notice infrastructure

2026-04-16 14:36:33 +02:00

integration

test(systemNotices): exclude v3 upgrade notices from login_count-only tests

2026-04-22 21:19:04 +02:00

unit

fix(journey): make sort_order authoritative for within-day entry ordering

2026-04-23 10:28:21 +02:00

websocket

test: expand test suite to 87.3% backend coverage

2026-04-06 20:08:30 +02:00

setup.ts

Add comprehensive backend test suite (#339)

2026-04-03 13:17:53 +02:00