Completed
Details
Assignee
UnassignedUnassignedReporter
Alex MillerAlex MillerLabels
Approval
OkPatch
CodePriority
MajorAffects versions
Fix versions
Details
Details
Assignee
Unassigned
UnassignedReporter
Alex Miller
Alex MillerLabels
Approval
Ok
Patch
Code
Priority

Affects versions
Fix versions
Created October 8, 2018 at 4:28 PM
Updated October 9, 2018 at 9:41 PM
Resolved October 9, 2018 at 9:41 PM
After the changes in 1.10 alphas, the cause is sometimes, but not always on the 2nd line of the error message. This should be standardized so the cause message is always on the 2nd line.
Before:
After:
Patch: clj-2415-5.patch
Changes (in order they occur in the patch):
For :read errors, move cause to 2nd line and remove "Cause: " at beginning
For rint errors, put exception class inside 1st line and move cause to 2nd line
For eval spec errors, use new message that includes fn and caller location
For eval non-spec errors, move exception class into 1st line and message on 2nd line
For macroexpand spec errors, omit spec ex-info msg which duplicates
For macroexpand non-spec errors, move message onto 2nd line and remove "Cause:"
For compile errors, move exception to 2nd line and remove "Cause:"