Clojurians Log v2

Is there a reason for the vector pairs here?

As I just tried

{& {:first_name ?first-name, 
                 :email !emails, 
                 :email_2 !emails, 
                 :phone !phones, 
                 :phone_2 !phones}}

Yes because as your map grows it will be parsed out of order and the memory variables will be in the wrong place. I think it is 8 elements when that happens?

Ah I see.

The … and lists are kind of apparent, but I don’t get how to use something similar with maps. If I have an input like

{:properties {:a {:type :int} :b {:type :string}}

{:properties 
 [{:name :a :type :int} {:name :b :type :string}]}

We just added map-of and sub map-of operators but you can also use seqable if you’re not in a situation to have multiple solutions

(m/rewrite {:properties {:a {:type :int} :b {:type :string}}}
  {:properties (m/map-of !name {:type !type})}
  {:properties [{:name !name, :type !type} ...]})
;; =>
{:properties [{:name :a, :type :int} {:name :b, :type :string}]}

(m/rewrite {:properties {:a {:type :int} :b {:type :string}}}
  {:properties (m/seqable [!name {:type !type}] ...)}
  {:properties [{:name !name, :type !type} ...]})
;; =>
{:properties [{:name :a, :type :int} {:name :b, :type :string}]}

One thing we haven’t gotten around to doing is making the

{& [[k v] ...]}

Thanks, that was much, much nicer that what we had. Will try this on deeper nested maps as well.

No problem. I’m here to help if I can. 🙂