You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cider-show-error-buffer and cider-auto-jump-to-error are customizable, but their semantics are a little too coarse-grained: one may not necessarily 'always or 'never want them to work.
A commonly desirable thing would be that one is presented detailed error reports on application-level exceptions. Compile-time exceptions would not deserve them, by default.
Therefore, we could make those two defcustoms have default value of lambda (exception-phase), and have the appropiate logic there.
NOTE: this GH issue is only concerned with not presenting stacktrace buffers when it's not particularly helpful.
Presenting a friendly, non-stacktrace-centric error report (e.g., turn clojure.core.specs.alpha/even-number-of-forms? into a pretty string / UI) would be done separately.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
cider-show-error-buffer
andcider-auto-jump-to-error
are customizable, but their semantics are a little too coarse-grained: one may not necessarily'always
or'never
want them to work.A commonly desirable thing would be that one is presented detailed error reports on application-level exceptions. Compile-time exceptions would not deserve them, by default.
Therefore, we could make those two defcustoms have default value of
lambda (exception-phase)
, and have the appropiate logic there.NOTE: this GH issue is only concerned with not presenting stacktrace buffers when it's not particularly helpful.
Presenting a friendly, non-stacktrace-centric error report (e.g., turn
clojure.core.specs.alpha/even-number-of-forms?
into a pretty string / UI) would be done separately.The text was updated successfully, but these errors were encountered: