Revert change that made fare_rules.txt conditionally required.
#359
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.
When the initial Fares v2 base implementation was added to the official spec (#286), it also included some changes for Fares v1. Specifically,
fare_rules.txtwas now marked as conditionally required iffare_attributes.txtis present. I believe this change was a mistake and should be reverted.It's my understanding that
fare_attributes.txthas always been allowed with a single entry to indicate a flat fare for all rides. In this scenario,fare_rules.txtis not required. This behavior was documented on the original Fare Examples wiki entry and has been (described elsewhere)[https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit#heading=h.1xji1nf0ko4z] as well. More importantly, I count ~40 feeds in the MobilityDatabase that are currently relying on this behavior.There was also a comment from @flocsy calling out this behavior in the original PR discussion (#286 (comment)), but I think it got dropped in the lengthy Fares v2 discussion?
Given all that evidence, my proposal is to revert the language change making
fare_rules.txtconditionally required.See also the related discussion in the #gtfs-fares slack channel and related discussion for the gtfs-validator.
gtfs-changes announcement: https://groups.google.com/g/gtfs-changes/c/Jn8OIuK6J54/m/RWg9hqwTBQAJ