Create a principled approach to error handling
Right now, we don't really have a good approach for handling invalid ipuz files. On some errors (such as json errors) we flag the file as being invalid. On others, we just ignore the error. Occasionally, we'll use a g_warning() as well.
We should come up with an approach that we can be consistent with. Do we want to be strict with what we parse, or do the best we can to produce a playable puzzle? We will almost certainly have to pipe GErrors more aggressively through the codebase regardless.
@federico Can I pick your brain about this over GUADEC?
Edited by Jonathan Blandford