Sorry for the delay in addressing this; been a bit away from KonOpas
coding recently.
I added a GitHub issue for this:
https://github.com/eemeli/konopas/issues/11
I agree that some error checking would be good. As the program &
participant data files are parsed as JavaScript, unfortunately many
errors will prevent it from loading properly, which doesn't
necessarily give much scope for pinpointing the source of the errors.
But some things could well be caught, like "id" being a number instead
of a string, or "loc" being a string instead of an array, or the error
types you mentioned.
I'd rather not add such error checking to the deployed version, but
with the current Makefile there are two build options for KonOpas,
"make dev" and "make prod". The first of those could be made to
include a data integrity scanner, as well as including it with the
online configurator:
http://konopas.org/util/config
I'd also rather not add error checking to the CSV to JSON(P)
converter, as at least for now it's a very generic tool rather than
being highly KonOpas-specific.
In any case, thank you, belatedly, for the suggestion!
eemeli
On 3 April 2014 17:24, Karl-Johan Norén
> --
> You received this message because you are subscribed to the Google Groups "KonOpas Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
konopas-dev...@googlegroups.com.
> To post to this group, send email to
konop...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.