I don't see us ever needing support for this, but technically there is an optional file in the schedule spec that's in JSON format instead of CSV format.
We would (to some degree) blow up if we ever tried to parse a schedule that defines it.
So in the case that the PVTA one day adds it to the schedule or if someone else ends up using this lib and they end up requesting support this is here. For now though, marking as wontfix.
I don't see us ever needing support for this, but technically there is an optional file in the schedule spec that's in JSON format instead of CSV format.
We would (to some degree) blow up if we ever tried to parse a schedule that defines it.
So in the case that the PVTA one day adds it to the schedule or if someone else ends up using this lib and they end up requesting support this is here. For now though, marking as wontfix.