Introduce the concept of 'warnings' for files with only slightly bad data

There have been various events that SplitsBrowser has encountered with 'minor' difficulties, such as problems with the data for one competitor. Perhaps the most recent example is event 9129 on splitsbrowser.org.uk, where a typo has led to a semicolon in someone's name. This errant semicolon in a file of semicolon-separated data caused everything else in this row to be 'out' by one cell.

To date, SplitsBrowser's response to event data like this has been to fail to load the entire event and issue an error instead. In this case, the problem affected only one competitor, and SplitsBrowser could recover by simply ignoring the errant line and moving on to the next, so reporting an error seems somewhat fussy.

Clearly, if there are serious problems with the data that prevents a large amount of it from being read, then the existing behaviour of reporting an error is still suitable. However, in a lot of cases it may be only a small number of competitors that would be affected, and it would seem better if SplitsBrowser could read the rest of data in.

LukeWoodward / SplitsBrowser

Introduce the concept of 'warnings' for files with only slightly bad data #49