Matt Bishop

I don't think Postgres is going to be able to implement the same 'exactly this array' semantics: https://www.postgresql.org/docs/13/datatype-json.html#JSON-CONTAINMENT

I am messing about with how to handle queries like `{ “an-array-field”: “$elemMatch”: { “$gte”: 4, “$le”: 6 } }` and am thinking generating JSONPath queries will be better, since...

@thomas4019 do you have a minimum Postgres version you want to support?

My attempts to use JSON Path mixed with other JSON operators has failed. I don't think it's possible to mix the two. Might be interesting to consider refactoring this lib...

Also, it separates the path from the value filter. `$.store.book[?(@.price

Promises cache their values by default, so multiple calls to resolve() return the first resolution result. It's like a Java Future that way. https://www.ecma-international.org/ecma-262/6.0/#sec-promise-resolve-functions

How about this error message @arichiardi? Doesn't PR #54 fix this one too?

So you're saying neither `Spec.or` nor `Spec.and` will work. Can you provide a link to the Clojure Spec docs section that shows how to do this?

Does this only apply to `map` specs?

It's not possible to merge specs like this. See also https://github.com/prayerslayer/js.spec/issues/51 for an idea on how this might be built.