Repository navigation
[NJ Transit] Fix breakage due to changes in the underlying Nuxt API - #808
Merged
Merged
Conversation
The regular train data notably has a unified Secaucus Junction Station while the departure vision which we're using has the separated Secaucus Junction Lower Level and Secaucus Junction Upper Level
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This gets the app working again after the Nuxt format was changed no longer have the "path" entry. In addition, we now look at the departure visions stations instead of all train stations too, which leaves the two distinct
Secaucus Junction Upper LevelandSecaucus Junction Lower Leveland no longer the combinedSecaucus Junction Station.