Giters
bhb
/
expound
Human-optimized error messages for clojure.spec
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
922
Watchers:
16
Issues:
81
Forks:
24
bhb/expound Issues
optional include location of the spec error in the message.
Updated
2 years ago
Comments count
2
Feature inquiry: a convenience function for validating a value against a spec
Closed
3 years ago
Comments count
4
proposal : defmsg equivalent for arbitrary predicates
Closed
3 years ago
Comments count
15
PersistentList cannot be cast to class Named
Closed
3 years ago
Comments count
3
ClassCastException from `expound-str` when running in AWS Lambda
Closed
3 years ago
Comments count
9
Wrapped `s/keys` does not properly display unqualified keyword specs
Closed
3 years ago
Comments count
5
Small *print-length* and/or *print-level* sometimes yield NPE
Closed
3 years ago
Comments count
5
Crash bug when printing, if a datomic db is present and the spec fails
Closed
3 years ago
Comments count
19
Internal error in `lift-singleton-groups` when having a datomic db value in fn args
Closed
4 years ago
Comments count
13
Error reports returned as :cause string in an exception when produced by instrumentation within generative testing
Closed
4 years ago
Comments count
11
should expound work anywhere s/explain works? - clojurescript error
Closed
4 years ago
Comments count
7
Error in :ret check when using with Orchestra 2020.07.12-1
Closed
4 years ago
Comments count
5
(cljs.spec.test.alpha/instrument) breaks expound due to wrong arity
Closed
4 years ago
Comments count
4
"Cannot convert path" on instrumentation failures in the wild
Closed
4 years ago
Comments count
4
`printer` has invalid spec
Closed
4 years ago
Comments count
2
Easier editing of error messages
Updated
4 years ago
Regression of #3
Closed
5 years ago
Comments count
4
Using expound printer for `instrument` exceptions in the browser
Closed
5 years ago
Comments count
2
Idea: improve error messages with compile-time information of the faulty expression
Updated
5 years ago
Comments count
7
Custom error messages for preds look weird
Closed
5 years ago
Comments count
2
Using `defmsg` can cause duplicate printing with `alt` spec
Closed
5 years ago
Comments count
1
`defmsg` only works for some types of specs
Closed
5 years ago
Comments count
8
ArityException when calling expound on a multi-spec with custom retag function
Closed
5 years ago
Comments count
2
Unnecessary dependency on `cider-nrepl`
Closed
5 years ago
Comments count
1
Improve grouping of spec errors
Closed
5 years ago
Comments count
2
should contain keys: summary could be improved [0.7.2]
Closed
5 years ago
Comments count
3
Internal Expound assertion failed using ring.core.spec
Closed
5 years ago
Comments count
6
Alternation for missing element doesn't display correctly
Updated
5 years ago
Comments count
1
consider shorting down error message on sequence failure
Updated
5 years ago
Comments count
10
allow passing options map to expound/expound-str
Closed
5 years ago
Comments count
1
alter-var-root suggestion doesn't seem to have any effect
Closed
6 years ago
Comments count
3
ClassCastException when expounding a map with a sorted-map value
Closed
6 years ago
Comments count
2
The explain-results function does not work with 1.10-alpha*
Closed
6 years ago
Comments count
6
Limitation on using conformed values limits usefulness of some `s/and` specs
Closed
6 years ago
Comments count
8
"Cannot convert path" when a failed spec contains `s/keys*`
Closed
6 years ago
Comments count
3
The expound/def macro does not work in ClojureScript
Closed
6 years ago
Comments count
9
ClojureScript warning: var is not public
Closed
6 years ago
Comments count
4
Try `figwheel.main` for tests and CLJS REPL
Closed
6 years ago
Comments count
3
Cannot add messages to predicates that are not yet declared specs
Closed
6 years ago
Comments count
1
logo design contribution
Closed
6 years ago
Comments count
1
When `keys` spec fails, the entire map is printed out (not the summary form)
Updated
6 years ago
Comments count
2
Integrate with clojure.test.check.clojure-test/defspec
Closed
6 years ago
Comments count
5
Emacs cider
Closed
6 years ago
Comments count
1
Errors with large data structures became harder to read
Updated
6 years ago
Comments count
1
Spec error refers to `:args` incorrectly
Closed
6 years ago
Comments count
5
Printing messages without newlines or separators
Closed
6 years ago
Comments count
4
Add documentation
Closed
6 years ago
Comments count
1
Npm packaging
Closed
6 years ago
Comments count
1
expound seems to print explain a problem twice whenever a compile time error is found
Closed
6 years ago
Comments count
7
consider making the `relevant specs` section optional
Closed
6 years ago
Comments count
5
Previous
Next