UI: Refactor SavedTripsScreen with Trip object and enhance interactions #259
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.
TL;DR
Refactored saved trips functionality and improved UI interactions.
What changed?
SavedTripUiEvent
to useTrip
object instead of string identifierstripId
property toTrip
class for easier identificationSavedTripCard
to acceptTrip
object instead of separate origin and destinationSavedTripsScreen
to handle card clicks and deletionsSavedTripsViewModel
for deleting and clicking saved tripsTimeTableViewModel
to usetripId
when saving tripsWhy make this change?
This refactoring improves the consistency and maintainability of the saved trips feature. By using the
Trip
object throughout the flow, we reduce the chance of errors and make the code more type-safe. The changes also enhance the user experience by providing more intuitive interactions with saved trips.