anchor.diff:  clj -X:my-fn
   ----
   
  -You can supply additional keys, or override values stored in the deps.edn file by passing  pairs of key-path and value. The key-path should either be a single key or a vector of keys to refer to a nested key (as with `assoc-in`). Each key-path will be used to `assoc-in` to the original `:args` map, overriding the value there.
  +You can supply additional keys, or override values stored in the deps.edn file by passing pairs of key-path and value. The key-path should either be a single key or a vector of keys to refer to a nested key (as with `assoc-in`). Each key-path will be used to `assoc-in` to the original `:args` map, overriding the value there.
  +
  +[source]
  +----
  +# Top key override
  +clj -X:my-fn :config 789
  +
  +# Nested key override
  +clj -X:my-fn '[:my :data]' 789
  +----
   
   Key/value pairs are read as edn strings, please see the tips about quoting below.
   
  
positive.code: 
  After installation, deps.edn configuration files can be found in (up to) three locations:
  
  - installation directory - created only at install time
  - config directory (often ~/.clojure) - modified to change cross-project (or no-project) defaults
  - the local directory - per-project settings
  
  The `deps.edn` files in each of these locations (if they exist) are merged to form one combined dependency configuration. The merge is done in the order above install/config/local, last one wins. The operation is essentially `merge-with merge`, except for the `:paths` key, where only the last one found is used (they are not combined).
  
  You can use the  `-Sverbose` option to see all of the actual directory locations.
  
  
negative.code: {:aliases
   {:my-fn
    {:fn my.qualified/fn
     :args {:my {:data 123}
            :config 456"}}}}
  ----
  
  To invoke, pass the name of the alias:
  