-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
gracefully handle errors for unsupported cabal version #4425
gracefully handle errors for unsupported cabal version #4425
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
c8db13a
to
1116c31
Compare
295dcb8
to
40173f4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One little improvement to the much appreciated error message!
Otherwise, LGTM and we can merge.
Sorry for not responding, and thanks for adding the last missing change! |
No worries, it is usually no hurry, but we likely will have a release soon, I would love to have this change in :) So rather, my apologies for just pushing changes without asking! |
b543998
to
12cbc38
Compare
Signed-off-by: Julian Kalema Lukwata <[email protected]>
12cbc38
to
869e8a3
Compare
* Safely handle linenumbering for errors in the first line of cabal files * add integration test for unsupported cabal version Signed-off-by: Julian Kalema Lukwata <[email protected]> * cast unsupported cabal version as warning * add better warning text * Add supported cabal-versions to the error message --------- Signed-off-by: Julian Kalema Lukwata <[email protected]> Co-authored-by: Fendor <[email protected]>
This PR makes sure that line number 0 returned from cabal is handled correctly.
This caused the marking of the whole cabal file if the cabal version is not supported as described in #4401