Custom `:parameter-aliases`

[onetom]

Custom `:parameter-aliases`

[oliyh]

Hello,

Yes, I am in favour of letting data flow through and for any 'enriching' to be additive and not destructive, so what you propose sounds good. If you make a PR, there is a spec at https://github.com/oliyh/martian/blob/master/core/src/martian/spec.cljc describing the martian input data structure, you'll need to update that to include the :parameter-aliases key.

Thanks

[onetom]

btw, currently im working the problem around by retouching the handlers of a bootstrapped martian api:

(defn req-param-alias
  "Attach a parameter alias for a martian handler."
  [martian-handler key-alias schema & param-key-path]
  (-> martian-handler
      (assoc-in [:parameter-aliases
                 schema
                 (vec (butlast param-key-path))
                 key-alias]
                (last param-key-path))))

(defn mk-api
  [api-url handlers opts]
  (-> api-url
      (martian/bootstrap handlers opts)
      (update :handlers
              (partial map #(req-param-alias
                              % :qb.company/realm-id :path-schema :realmId)))))

but this adds an extra wrapper layer around martian.core/bootstrap...