-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[FEEDBACK] Update TfL Widget - Elizabeth line #997
Comments
This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days. |
still relevant |
This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days. |
This issue was automatically closed because it has been stalled for over 6 weeks with no activity. |
Hey @ramzh, I am SO sorry for the late reply here. I agree it's inconsistent, but it is actually correct. This is because according to TfL it isn't technically a Tube line, since most of the route uses the National Rail network and infrastructure, and because the British Rail Class 345 trains which service the line are much larger than Tube trains. Even the official TfL Status page calls it "Elizabeth Line" when all others are just called Central, District, Piccadilly, etc Dashy is calling the API like this: |
Hey Lissy!
Love your work and truly amazing with the widget. As a Londoneer myself , I set up the TfL widfget however I noticed that the Elizabeth line does not follow the same schema name as the others in the widget and widget options
Would it be possible to update the widget and widget option to accept "Elizabeth" as option name? :)
Thanks again for the awesome tool!
The text was updated successfully, but these errors were encountered: