More feeds appear to be using whitespace in their CSV, (issues #56, #64), causing issues when processing the values. This adds the skipinitialspace option to the CSV reader, stripping them before we get to value processing.
I've also gotten qa_check.sh running cleanly again.
Coverage remained the same at 100.0% when pulling 4de1064cc182d82ce4eb3b8c88adfefa02fc9bc7 on jwhitlock:optional-whitespace into 434fd5b0fe1d2b0c571e37ac700a1c0e3b3332d9 on tulsawebdevs:master.
Coverage remained the same at 100.0% when pulling 4de1064cc182d82ce4eb3b8c88adfefa02fc9bc7 on jwhitlock:optional-whitespace into 434fd5b0fe1d2b0c571e37ac700a1c0e3b3332d9 on tulsawebdevs:master.
Coverage remained the same at 100.0% when pulling 9c2ea6af8e2a7c27d00b2fba330cf2b64aee0084 on jwhitlock:optional-whitespace into 434fd5b0fe1d2b0c571e37ac700a1c0e3b3332d9 on tulsawebdevs:master.
More feeds appear to be using whitespace in their CSV, (issues #56, #64), causing issues when processing the values. This adds the skipinitialspace option to the CSV reader, stripping them before we get to value processing.
I've also gotten
qa_check.sh
running cleanly again.