Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error messages #15

Open
setzer22 opened this issue Apr 26, 2016 · 3 comments
Open

Better error messages #15

setzer22 opened this issue Apr 26, 2016 · 3 comments

Comments

@setzer22
Copy link

setzer22 commented Apr 26, 2016

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!

@aengelberg
Copy link
Owner

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.

@marco-m
Copy link

marco-m commented Aug 12, 2017

Hello Alex, any progress on this? thanks!

@boxxxie
Copy link

boxxxie commented Jan 3, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants