binaryage / binaryage/cljs-devtools

Custom formatter for ex-info thrown by cljs.spec

Ouverte
#23 8 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
cljs-bug enhancement
Langage dominant
Clojure
Étoiles
1.1k
Forks
51
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Currently it's quite tricky to get good output from cljs.spec. Reason being that the ex-info thrown includes the full spec commentary in ex-message. This includes the serialised val which failed. In my case this can fill the console many times over.

Alex Miller recommended catching these exceptions and using the ex-data to present the spec nicely. (e.g. don't print the ex-message to the console). This would be fine except it's difficult to catch all errors due to the nature of how UI code executes (react render loop, re-frame dispatch queue, callbacks)

How about automatically detecting and pretty formatting ex-info errors thrown by cljs.spec?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

The issue names no files, tests, or entry points. Start by locating where cljs-devtools handles uncaught errors from UI render loops, re-frame dispatch queues, and callbacks, then determine how cljs.spec ex-info can be identified and formatted without printing ex-message. Done means the behavior is defined and covered for the described error paths.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
clojure
Domaine
devtools
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.