Skip to content
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

Use "Southbound" for Red Line non revenue trains #872

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

PaulJKim
Copy link
Collaborator

Summary of changes

Asana Ticket: Use "Southbound" instead of Ashmont/Braintree for non-revenue trains

Adds take 891 which announces Ashmont and Braintree Red Line passthroughs as "Southbound". Also adjusts the TTS codepaths to do the same.

Reviewer Checklist

  • Meets ticket's acceptance criteria
  • Any new or changed functions have typespecs
  • Tests were added for any new functionality (don't just rely on Codecov)
  • If signs.json was changed, there is a follow-up PR to signs_ui to update its dependency on this project
  • This branch was deployed to the staging environment and is currently running with no unexpected increase in warnings, and no errors or crashes (compare on Splunk: staging vs. prod)

@PaulJKim PaulJKim requested a review from a team as a code owner January 15, 2025 20:00
if audio.destination in [:ashmont, :braintree],
do: PaEss.Utilities.train_description(:southbound, audio.route_id),
else: PaEss.Utilities.train_description(audio.destination, audio.route_id)

Copy link
Collaborator

Choose a reason for hiding this comment

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

There's a bit of logic in Signs.Utilities.Predictions.prediction_passthrough_audios that does some munging of the destination, which should be updated. Actually, that might be a more natural place to override the destination to :southbound, and then this module could directly map that.

@dmaltzan
Copy link

@panentheos I checked in with Shanti and she'd like us to put this into production on 1/28 to align with a meeting that she's going to have with the OCC to fill them in on this. Can we plan for that?

Copy link
Collaborator

@panentheos panentheos left a comment

Choose a reason for hiding this comment

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

Looks good! See the note above that's we'd like to hold this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants