aligning stoptime stop_id/location_id/location_group_id && alternate_stop_name_exceptions.txt with spec #231
Conversation
This file contains 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
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.
Summary:
according to spec:
file - alternate_stop_name_exceptions.txt, fields - route_id && stop_id allow for non-numerical values in spec
file - location_groups.txt, field - location_group_name is an optional field
merge process was propagating stop_id value to location_id, & location_group_id (which are all supposed to be mutually exclusive)
Expected behavior:
Explain how you expect the pull request to work in your testing (in case other platforms/versions exhibit different behavior).
Please make sure these boxes are checked before submitting your pull request - thanks!