Skip to content

cider-show-error-buffer/cider-auto-jump-to-error: honor :clojure.error/phase #3418

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
vemv opened this issue Aug 19, 2023 · 0 comments · Fixed by #3423
Closed

cider-show-error-buffer/cider-auto-jump-to-error: honor :clojure.error/phase #3418

vemv opened this issue Aug 19, 2023 · 0 comments · Fixed by #3423
Assignees

Comments

@vemv
Copy link
Member

vemv commented Aug 19, 2023

See also: #3338

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.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant