-
Notifications
You must be signed in to change notification settings - Fork 80
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
Support Exception Based Scheduling #999
Conversation
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.
Big lift, thanks for the effort! Looks good, just a few sanity checks
</BsLabel> | ||
</> | ||
: <> | ||
<Icon type='warning' />(Exception based calendar) |
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.
Does this look good?
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.
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.
Could we add a space between the icon and the text?
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.
yes, yes we can
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.
We can even do some i18n in 369f85f
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.
To be brief, we could say [Name] (Exception)
Or is Exception based calendar
a commonly used term?
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 think Exception based calendar is more clear for the user. We can maybe wait for some feedback if people find it cumbersome
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.
Tested to the extent I understand what is going on
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.
This looks good! The UI makes sense when testing some cases. Feel free to address the few validation things we noticed
<BsLabel | ||
title={`Calendar has trips for ${routeCount} routes`}> | ||
<Icon type='bus' /> {routeCount} | ||
</BsLabel> **/} |
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.
Why is this commented out?
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.
Not sure, that's historical. But it seems at one point we displayed the number of trips for a calendar by routes, rather than patterns.
Checklist
dev
before they can be merged tomaster
)Description
This PR provides client support for exception based scheduling. To create an exception based schedule, either import a feed with calendar_dates based service or create a new exception of the new "Exception Based Service" type (or both!).
Relies on:
ibi-group/datatools-server#545
conveyal/gtfs-lib#385