Release Notes: v1.0.0¶
This introduces changes included in the following PRs:
Summary¶
- Replaced the custom Cumbria-only A* pathfinding engine with BRouter for faster routing across the whole of the UK and Ireland
- Added client-side validation to prevent identical start and end coordinates from being submitted
- Fixed coordinate input error states so they correctly clear when a route is cleared or the home/reset action is used
- Resolved broken tours on mobile
Changes¶
BRouter routing engine integration (#150)¶
- Removed the previous custom graph-based pathfinding and graph-generation code (preserved in the Crestr Legacy repository)
- Added a BRouter adapter so responses match the existing FastAPI routing endpoint format
- Introduced a hiking profile and BRouter service configuration (including example env files and Docker updates)
- Expanded location checks and search from Cumbria-only to the UK and Ireland
- Updated elevation handling, coordinate helpers, and related documentation/README coverage
Identical start and end coordinates (#155)¶
- Added a check that rejects an end coordinate matching the start coordinate
- Shows a clear error toast, clears the end entry, and prevents the route request from being sent to the backend
Coordinate input error state on clear/reset (#156)¶
- Extracted a shared
resetCoordInputStatehelper that clears error classes, restores placeholders, and resets input values - Called the helper from both the clear-route action and the home/reset action so error states no longer persist incorrectly
Tours on mobile (#161)¶
- Fixed broken in-app tours on mobile devices by differentiating between mobile and desktop / laptop devices, using a different mobile-specific tour for such devices
Why this matters¶
- Switching to BRouter removes the previous geographic limitation and delivers faster, more capable routing across the UK and Ireland, the largest functional expansion since the mobile interface.
- Preventing identical start/end coordinates stops confusing backend errors and gives users immediate, clear feedback.
- Correctly resetting coordinate input error states removes friction after clearing or resetting a route.
- Restoring working tours on mobile improves onboarding and feature discovery for users on phones and tablets.