Thanks!
Just fixed the warning, will go out with the next release.
-Jason
On Mon, Oct 26, 2015 at 5:44 PM, Jason Felice
wrote:
> It works great. All I did was updated project.clj, replaced s/both with
> s/constrained and removed the s/pred around the arguments, and it all
> worked.
>
> One l
It works great. All I did was updated project.clj, replaced s/both with
s/constrained and removed the s/pred around the arguments, and it all
worked.
One little weird thing: It now complains:
WARNING: atom already refers to: #'clojure.core/atom in namespace:
schema.core, being replaced by: #'sche
Thanks!
I'll try it out this week and let you know.
On Sun, Oct 25, 2015 at 8:28 PM, Jason Wolfe wrote:
> FYI -- we just released Schema 1.0.2, which adds `s/constrained` for
> postconditions.
>
> -Jason
>
> On Thursday, September 3, 2015 at 3:05:29 PM UTC-3, Jason Felice wrote:
>>
>>
>> On Wed
FYI -- we just released Schema 1.0.2, which adds `s/constrained` for
postconditions.
-Jason
On Thursday, September 3, 2015 at 3:05:29 PM UTC-3, Jason Felice wrote:
>
>
> On Wed, Sep 2, 2015 at 9:56 PM, Jason Wolfe
> > wrote:
>>
>> Outside of that, I can still potentially see the desire to spec
On Wed, Sep 2, 2015 at 9:56 PM, Jason Wolfe wrote:
>
> Outside of that, I can still potentially see the desire to specify
> postconditions rather than preconditions (you'd rather see an error (not
> (integer? "1")) than (throws? (odd? "1")), which will be the behavior when
> the bug is fixed. We'
Hi Jason,
That's a great question, thanks.
The exception you point out is just a
bug: https://github.com/Prismatic/schema/issues/263. Preconditions
currently wrap exceptions and return sensible validation errors, we just
missed this in guards. Will address this ASAP and cut a new release.
Hi Matt,
Thanks for the report.
I just tried and I'm unable to reproduce. Can you please open an issue on
the schema github project with your project.clj and the results of `lein
deps :tree` and we'll look into it ASAP?
Thanks,
Jason
On Wednesday, September 2, 2015 at 7:14:21 PM UTC-7,
I just created a scratch project using schema-1.0.0. Requiring schema.core
works fine, but coerce throws an exception. Here's the repl session:
user=> (require '[schema.core])
nil
user=> (require '[schema.coerce])
CompilerException java.lang.RuntimeException: No such var: s/spec, comp
I have a question: "both" is deprecated with a note to use "s/conditional"
instead. However, that doesn't work for my case.
I have the following: (s/both s/Int (s/pred pos?))
If I rewrite it to (s/conditional pos? s/Int), this throws:
(s/check (s/conditional pos? s/Int) "")
Since (as far as I
Awesome and good work! Can't wait to try it out.
- Matt
On Tuesday, September 1, 2015 at 2:02:30 PM UTC-4, Jason Wolfe wrote:
>
> We're excited to finally bring Schema out of alpha, while introducing some
> new exciting features around testing: test.check integration and data
> completion. Che
We're excited to finally bring Schema out of alpha, while introducing some
new exciting features around testing: test.check integration and data
completion. Check out the blog post for details about these new
applications.
http://blog.getprismatic.com/schema-1-0-released/
We've also rewritten
11 matches
Mail list logo