Miikka Koskinen

Hi, the generated output is valid for JSON Schema Draft 04.

That sounds like a good solution, a PR would be certainly welcome.

Considering that the new drafts are not backwards-compatible, I think the way to go is not to upgrade the current implementation but *add* support for the new version, for example...

Just to clarify: #173 is not a duplicate of this issue and merging data-spec still does not work.

Hi! I'm not very familiar with Avro, but I think it would be a good fit. Avro is somewhat popular, it matches Clojure datatypes okay, and looks like the implementation...

JSON object keys are strings, so the correct result would be like this: ```clojure user=> (j/write-value-as-string {'(:key) :value}) "{\"(:key)\":\"value\"}" ```

Doo does not use lein-cljsbuild for building even though it reads the `:cljsbuild` key in project.clj. Which is to say that the same problem might need to be fixed in...

@ericnormand, at the moment Sieppari supports choosing your own async library - there's support for Manifold, core.async and Promesa in addition to using `future`. Which of course make this issue...

Right, the async implementation is even more broken than I realized. W.r.t to using `future` for all async calls: How it's *supposed* to work is that if you return e.g....

My thought is: it won't help, because scjsv 0.6.0 still transitively depends on Guava 16.0.1. However, if we created a new release of scjsv that depended on json-schema-validator 2.2.13, that...