feat: Rename existing stop page to legacy stop page #554
Conversation
This file contains 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
EmmaSimon
force-pushed
the
es-legacy-stop-page
branch
3 times, most recently
from
94a101f
to
043fdbe
Compare
Trip details are not added included in this.
EmmaSimon
force-pushed
the
es-legacy-stop-page
branch
from
043fdbe
to
39ce0ae
Compare
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
Ticket: Combined stop + trip details: barebones UX
Precursor to #551, this doesn't add anything new to the copy pasted stop page, just builds a new route to prepare for the combined stop page, and a feature toggle to start using the new route.
- [ ] If you added any user facing strings on iOS, are they included in Localizable.xcstrings?Testing
Updated all existing tests to pass.