Remove direct public OSRM routing from Mobile - #262
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
cached_osrm_routepreferenceCloses #259
Parent epic: #253
Coordinated release: stef-k/Wayfarer#505
Validation
git diff --check 421cd736...HEADpassedDatabase / migration notes
cached_osrm_routepreferenceUI evidence
No screenshots are required: the change removes a provider path and retains the existing navigation presentation. Direct guidance is now explicitly classified and its lifecycle is covered at the production service seams.
Release boundary
This PR does not implement authenticated Wayfarer routing (#260) or retained-route persistence (#261). After merge, Mobile supports valid saved Segment geometry or local Direct guidance with no direct routing-provider contact.