Closed flibbertigibbet closed 4 years ago
One more thing. In the list view, we should render "Multiple destinations" where the single-destination name would be. Same typography as single destination. Not linked.
Updated layouts:
List view:
Detail view:
That looks great!
Nice catch @maurizi! I should've seen that 🤦♂
@flibbertigibbet Doesn't look like the latest changes you made were pushed, though it looks like they may still contain the regression @maurizi reported.
@lederer thanks for pointing it out. I'd pushed to my working branch, but not the upstream copy on this repo (for the tests to run). I've pushed upstream.
Fixed the layout for the longer event names that fortunately appeared on staging:
Overview
Hide the destination for events that have multiple destinations.
Instead, show a message indicating that the event has multiple destinations, and link to the website details page.
Demo
Destination not listed on event in list view:
Notes
Since we are not fully implementing the new tours and multiple-destination events features in the Android app, instead we're simply hiding the destination from events that have more than one.
The old
destination
property is still present on the API response, and corresponds to the first destination when there are multiple.Testing
Testing this will require using the staging endpoint. Note that the one event currently on staging with multiple destinations is the one pictured above ("We Walk PHL in the Woodlands").
WEBSERVICE_URL
inDestinationWebservice.java
here to point to https://staging.gophillygo.org/.website_host
string added tostrings.xml
here to point to staging (used to link out to the event details page).Closes #173.