loco
loco copied to clipboard
Better error messages
I find that while your library is really easy to use, the slightest error in the model generation results in an incomprehensible error message that arises from the inner implementation.
The one I'm seeing the most is:
No method in multimethod ->choco* for dispatch value: <whatever>
I think proper model validation and error messages would make a very nice addition to an otherwise awesome library!
Thanks, I definitely agree that's an issue with Loco at the moment. It'll require some thought to determine how to add enough validation to every constraint to prevent these types of errors.
Hello Alex, any progress on this? thanks!
I'm actually working on a possible solution to this, by putting pre conditions on the constraint functions, and I have loco produce something like pseudo code that can have validation functions run against it. at the very least one can look at the output and see if it makes sense.