-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue with latest (1.10.x) cljs versions #174
Comments
afaik, bidi is the only thing using schema in my project, so that's why i suspect it |
I would suspect bidi is using a rather old version of schema. It looks like
there was a recent release, if you explicitly depend on 1.1.7 of
prismatic/schema, does it go away? If so we can bump the version.
…On 20 March 2018 at 22:50, David Meister ***@***.***> wrote:
afaik, bidi is the only thing using schema in my project, so that's why i
suspect it
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#174 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AF2h2hXZmYud-HUnQWbW068G6C9GR6gTks5tgYengaJpZM4Syxfq>
.
--
Dominic Monroe
Developer
Email: [email protected]
Web: https://juxt.pro
JUXT LTD.
Software Consulting, Delivery, Training
|
We could consider removing schema.core from bidi altogether, it's not used very much. |
is it something spec could handle? |
Introducing spec would mean that bidi required 1.9.0 as a minimum. That would be a breaking change. Then again, removing schema is also a breaking change. |
mmm true, but it also removes a dependency on a third party lib |
You can add clojure-future-spec to allow bidi to be compatible with 1.8 and use specs fyi. |
Many warnings being dumped out in the latest version of cljs, not sure if an issue with bidi or schema or both:
The text was updated successfully, but these errors were encountered: