-
Notifications
You must be signed in to change notification settings - Fork 35
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
Unified error terms and text #49
Comments
For a type error on the form of an expression E not matching a type T, I suggest the simple structure |
@josefs can we get your blessing to make this happen? I expect that I can dish out a PR addressing this issue before the week ends if we can agree on the format. |
I can answer yes on this question. Almost certain that Josef doesn't mind that you sort this out! |
@Zalastax, go wild! I'd love to see this happen. |
It would be good to have an option to return errors as erlang terms (when called from Erlang, not cli).
This requires unifying and documenting the error terms, each one having the same structure (common fields in same position: eg filename, line number, expected type etc.)
Also the default formatter (used by the cli) could have a format similar to other tools, like the compiler:
file-name:line-number:error-text
The text was updated successfully, but these errors were encountered: