-
Notifications
You must be signed in to change notification settings - Fork 22
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
Simplified formatting for deppy.NotSatisfiable
error
#151
Comments
I really like how
Or more complex one:
|
This repo with examples on how to format errors might be useful: https://github.com/perdasilva/deconflictor. |
I updated the description of the issue beucase it was initially not factually true: I origianlly said that I think readability of |
I think we have overlooked this particular aspect as well. We should define a standard for how to structure IDs and perhaps add a package (not sure where) to help users build IDs that will be easier to reason about. |
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the |
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the |
Today
deppy.NotSatisfiable
is being formated in a not very human friendly way: it is challenging to understand what exactly went wrong from the error message.We need to explore error formatting options which:
This probably should be plugable.
The text was updated successfully, but these errors were encountered: