-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Itinerary Body Caret Improvements #685
Itinerary Body Caret Improvements #685
Conversation
version "11.1.2" | ||
resolved "https://registry.yarnpkg.com/@opentripplanner/core-utils/-/core-utils-11.1.2.tgz#a99d1fa4fb1f587d58fae8fcfd70a3bfe4eed424" | ||
integrity sha512-Rn1tBm5F+nt/A4/0cpq6cyNTprSsxfFslujMoZ4P4r6fZ7YTx0d25di+MZ/CZgSlCzHJIiGAfi8DsfJ7yStcTA== | ||
"@opentripplanner/geocoder@^1.4.2": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's up here!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick q about the alerts!
@@ -300,7 +300,9 @@ class TransitLegBody extends Component<Props, State> { | |||
alertCount: alerts.length | |||
}} | |||
/> | |||
<S.CaretToggle expanded={alertsExpanded} /> | |||
{!shouldOnlyShowAlertsExpanded && ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait doesn't shouldOnlyShowAlertsExpanded
just impact how the alerts are rendered? The caret should still be there if users want to collapse them after render, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That behavior doesn't work right now
graphql "^16.6.0" | ||
lodash.clonedeep "^4.5.0" | ||
lodash.isequal "^4.5.0" | ||
qs "^6.9.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow good job cleaning up the dependencies with this pr
The itinerary body previously showed carets when they were inoperable. This PR ensures they are only shown when it makes sense