I see that this handler uses `ex-str`, which is nice because `ex-str` in
turn calls `*explain-out*` which is user-configurable.
Is there a recommended way to configure `s/*explain-out*` such that this
configuration will be run before other namespaces are loaded?
For instance, this code would s
Very cool! Excellent work.
On Monday, December 11, 2017 at 7:23:38 AM UTC-7, OHTA Shogo wrote:
>
> Hi, all
>
> I’m happy to announce the first release of Pinpointer, yet another
> implementation of spec error reporter based on a precise error analysis.
>
> - https://github.com/athos/Pinpointer
Thanks Juan! This works in Clojure, but it doesn't work for me in
Clojurescript due to the use of "resolve"
" Assert failed: Argument to resolve must be a quoted symbol"
This is where I got stuck too.
It looks like spec does have access to the predicate at runtime (after all,
it can figure ou
I ran into a case today where I mistyped the keyword in a `keys` spec and
was surprised that validation was not catching invalid data. For my
purposes, it would be sufficient to have a automated test that looks at my
specs and identifies typos in the spirit of
https://gist.github.com/stuarthall
> On Tue, Jul 25, 2017 at 4:16 PM, Ben Brinckerhoff > wrote:
>
>> Expound formats clojure.spec errors in a way that is optimized for humans
>> to read. Expound works in Clojure and Clojurescript.
>>
>> This release provides human-optimized error messages when
Expound formats clojure.spec errors in a way that is optimized for humans
to read. Expound works in Clojure and Clojurescript.
This release provides human-optimized error messages when using a number of
spec features, including instrumentation and `assert`.
More information is available in the
same way, which it currently doesn't because it just
> reports [key].
>
> Juan
>
> El jueves, 13 de julio de 2017, 11:27:44 (UTC-3), Ben Brinckerhoff
> escribió:
>>
>> No, you're not missing anything. I've run into the same issue. I see
>> you&
No, you're not missing anything. I've run into the same issue. I see you've
found the related JIRA issue, but for those who haven't it's
https://dev.clojure.org/jira/browse/CLJ-2192
> So the thing is that if you see a problem in [::k 1] you don't know if
its the ::k value, or the value is a seq
Figly is building the next-generation platform as a service (PAAS) to
transform enterprise software. We are led by a world-class team with a
track record of successful cloud startups, as well as leadership experience
at the largest software companies.
The platform includes a native mobile clien
The eastwood linter can also be configured to look for possibly misspelled
keyword typos
https://github.com/jonase/eastwood#keyword-typos
On Friday, February 3, 2017 at 3:47:21 AM UTC-7, John Schmidt wrote:
>
> I suggest something like (defn fetch-encrypted [] (fetch-important-data
> {:encrypt
I would certainly welcome and use an `overinstrument` function if added to
schpec (or another library).
One reason spec is great because it provides "a la carte" validation: a can
add an appropriate amount of validation to the parts of my code that would
most benefit from it. In my experience u
On my team, we tried using RoboVM to compile Clojure to iOS. It worked fine
once it booted, but startup time was a concern. We didn't spend a lot of
time optimizing it though. We also found the compile/boot cycle to be quite
long (over 50s to see a change). My understanding (perhaps mistaken) is
> the database as a dependency is enough to help testing use-cases and
> overall code decoupling, and the implementation is all hidden behind a set
> of protocols specific to our app.
>
>
> On Thu, Oct 31, 2013 at 6:31 AM, Jozef Wagner
>
> > wrote:
>
>> Followin
Clojure is the first functional programming language I've used for anything
more than toy examples, so I'm learning functional programming in general
as well as Clojure specifically. I understand the value of creating pure
functions in theory, but when writing applications, I'm finding that logi
14 matches
Mail list logo
