On Tuesday, 20 February 2018 12:10:01 UTC-5, Luke VanderHart wrote:
>
> You're very likely correct about shutdown-agents, I don't think I happened
> to fire up any agents in my test code. I'll try to reproduce as soon as I
> get a chance.
>
FWIW, I’m seeing the same delay, and my project doesn’t
tiistai 20. helmikuuta 2018 19.05.55 UTC+2 Alex Miller kirjoitti:
>
>
> On Tuesday, February 20, 2018 at 10:28:12 AM UTC-6, Erik Assum wrote:
>>
>> FWIW, I’ve been using https://github.com/metosin/spec-tools
>> on a couple of projects lately, which helps nicely with
>> conformance and coercion. The
Just out of curiosity, are there any plans to provide similar tooling
consistent with this for ClojureScript unit tests via Clojure Deps?
On Tue, Feb 20, 2018 at 9:10 AM, Luke VanderHart
wrote:
> You're very likely correct about shutdown-agents, I don't think I happened
> to fire up any agents i
I struggled for a long time with Clojure and experiencing some of the power
that I had heard about form others. I realize now that it was because I
had been so ingrained in the OO paradigm that I wasn't coding in the way
that Clojure wanted me to.
Anyway, I've since overcome that and now that
Calling s/valid? will tell me if the data is valid *if it has been conformed*.
But what if it hasn't? Can I use the data? Is it "valid" according to the spec
I wrote?
If your spec includes coercions, you have inherently made the “is valid?”
question include the coercion. Your ::test-spec accept
On Tuesday, February 20, 2018 at 11:24:19 AM UTC-6, Erik Assum wrote:
>
> Out of curiosity, are you at liberty to discuss how Cognitect solves the
> problem of validating/coercing values at the edges of the application when
> you (Cognitect) are doing consulting?
I'm not involved with those t
Out of curiosity, are you at liberty to discuss how Cognitect solves the
problem of validating/coercing values at the edges of the application when you
(Cognitect) are doing consulting?
Erik.
--
i farta
> 20. feb. 2018 kl. 18:05 skrev Alex Miller :
>
> I do see the problems driving this, and
You're very likely correct about shutdown-agents, I don't think I happened
to fire up any agents in my test code. I'll try to reproduce as soon as I
get a chance.
On Tuesday, February 20, 2018 at 11:25:01 AM UTC-5, Eli Naeher wrote:
>
> I love this, and have set it up in our latest project along
On Tuesday, February 20, 2018 at 10:28:12 AM UTC-6, Erik Assum wrote:
>
> FWIW, I’ve been using https://github.com/metosin/spec-tools
> on a couple of projects lately, which helps nicely with
> conformance and coercion. The main devs are very helpful on #ring-swagger
> on the Clojurians slack.
>
FWIW, I’ve been using https://github.com/metosin/spec-tools
on a couple of projects lately, which helps nicely with
conformance and coercion. The main devs are very helpful on #ring-swagger on
the Clojurians slack.
Alex, how does spec-tools measure up to your thoughts on conformance/coercion?
E
I love this, and have set it up in our latest project alongside Lein.
I've noticed a delay (~60s) after the tests finish and the results are
reported before the process exits. I'm wondering if there's a missing
call to shutdown-agents somewhere. Adding it to a shutdown hook doesn't
seem to have an
On Friday, 16 February 2018 09:47:30 UTC-5, Luke VanderHart wrote:
>
> The goal is to have a full featured, standardized test runner on a project
> using basic Clojure Deps, without needing to introduce Boot or Leiningen
> just for that.
>
This is great to see — I’ll give it a try — thanks!
———
This is exactly why we recommend that you not use conformers for coercion.
Conformers were added primarily as a tool for building custom composite
spec types (for example, we used it to build keys* from keys).
This is a common need though and I would be happier if spec did more to
help you solv
Looks very useful. One suggestion: the example might be easier to read if
you included the values of the env vars, and clarified the way you specify
default values:
{:connection-pool
{:user-name #dyn/prop [DB_USER "accountsuser"] ; default value
"accountsuser"
:user-pw #dyn/prop DB_PW
I've been using spec for a while now, in a reasonably large code base (>30k
lines of Clojure and ClojureScript) and there is an issue that bit me
several times.
I use conformers for coercing data that is *almost* what I need, usually
when reading from JSON (RethinkDB). Common conformers are key
Clojure does not have Python's triple-quoted strings, that is true. Why?
They have only come up a few times before in discussion on this Google
group, and Rich Hickey has not participated in them that I have seen, so
most likely he may simply not see much advantage to having them in the
language,
Just like r"" or r""" """ in python.
r"""{"doc":"This is a JSON string."}"""
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be pati
17 matches
Mail list logo
