Skip to content

Conversation

@landonreed
Copy link
Member

Fixes #268. A previous attempt had tried to fix this by connecting the RealtimeTimeColumn to the redux store, but the true underlying issue was a bad destructuring of props in TabbedItineraries.

To test, use a config.yml for a timezone different than your local computer's. Plan a trip and verify that the times in the narrative itinerary match what is shown in the tabbed-itin summary.

Copy link
Collaborator

@binh-dam-ibigroup binh-dam-ibigroup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Turned out better than what I thought!

@binh-dam-ibigroup binh-dam-ibigroup removed their assignment Oct 30, 2020
@evansiroky evansiroky merged commit ae0e668 into dev Nov 2, 2020
@landonreed landonreed deleted the fix-time-format branch November 2, 2020 20:23
@landonreed landonreed mentioned this pull request Nov 9, 2020
@landonreed
Copy link
Member Author

🎉 This PR is included in version 1.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Mismatched time values in Itinerary Narrative vs. Tabbed Summary

4 participants