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 detection and notification #82

Open
mightybyte opened this issue Feb 12, 2014 · 1 comment
Open

Better error detection and notification #82

mightybyte opened this issue Feb 12, 2014 · 1 comment

Comments

@mightybyte
Copy link
Contributor

In cases where your markup has inconsistencies the error detection/notification is really bad. I've been bitten numerous times by these problems and they are pretty hard to track down. I don't have any concrete suggestions right now. Just wanted to start a dialog.

@mightybyte
Copy link
Contributor Author

I looked into this a little more, and it seems like much of the problem is related to error handling with the "error" function. I fixed this in df-heist here:

Soostone@bbb129d#diff-a32ca51d16d0f098cf27e8e7d3c682f3L168

But there are still a bunch of places in the main library where error is used. The next major release of heist will have built-in error handling facilities, so from the df-heist standpoint I'll be able to deal with failure in a principled way. It would be really nice of df itself could transition to Either String functions so we can catch more error conditions in this way.

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

1 participant