You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the list of validation issues for a given feed version, there is no indication of priority given to the various issue types. In other words, there is no way to distinguish whether an issue could be considered an error vs. a warning -- e.g., something that would break feed ingestion by a third party service vs. just affect how a name field might be rendered.
We already have a measure of priority stored in the gtfs-lib class that deals with validation issues. We just need to display this in the UI using either the binary error vs. warning classification or the multi-tiered priority classification.
The text was updated successfully, but these errors were encountered:
In the list of validation issues for a given feed version, there is no indication of priority given to the various issue types. In other words, there is no way to distinguish whether an issue could be considered an error vs. a warning -- e.g., something that would break feed ingestion by a third party service vs. just affect how a name field might be rendered.
We already have a measure of priority stored in the gtfs-lib class that deals with validation issues. We just need to display this in the UI using either the binary error vs. warning classification or the multi-tiered priority classification.
The text was updated successfully, but these errors were encountered: