-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add a delays page for alert analysis #997
Conversation
return ( | ||
<ChartBorder> | ||
<div className={classNames('h-72', 'flex w-full flex-row')}> | ||
<Line |
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'm curious if TimeSeriesChart.tsx
would work for your purposes. I've been hoping we could consolidate some of the chart.js boilerplate into this component, and I had success using it for some of the newer service/ridership graphs. Not a big deal either way (but if you try it and find that it's not working somehow, I'd love to know why!)
This closes #986, right? |
Yep @rudiejd, that's the plan |
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 do think this PR is a little too big and could benefit from separating the server changes from the FE changes. But LGTM 🚢
Backend changes in #1011 to shrink this PR |
Motivation
#986
Keep track of what is keeping the MBTA from reliably delivering service on each line
Changes
Testing Instructions
Requires data from transitmatters/data-ingestion#104 and transitmatters/data-ingestion#113 before being merged