upgrade schedule validator to v4.0.0 #1973
Merged
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.
Description
See the validator release notes for the full list of changes. Per our Slack discussion we are choosing to just upgrade in-place rather than backfill and/or keep two versions of validations over the same data. We can still choose to do that in the future, and we will probably need to do something similar with the reports site so old reports are not updated.
In addition, we can't even really backfill accurately if we wanted to; it would lead to inaccurate notices that rely on the "current date" when executing, such as feed expiration. I created MobilityData/gtfs-validator#1292 to track the need for a "time of validation" input which would facilitate backfills.
Resolves #1924
Type of change
How has this been tested?
Locally; I've verified the validator runs and the external table can be queried.
Screenshots (optional)