commando.impl.utils — org.clojars.funkcjonariusze/commando 1.0.4

*execute-config* clj/s

Dynamic configuration for commando/execute behavior.

• :debug-result (boolean): When true, adds additional execution information to the returned status-map, aiding in instruction analysis.
• :error-data-string (boolean): When true, the :data key in serialized ExceptionInfo (via commando.impl.utils/serialize-exception) will be a string representation of the data. When false, it will return the original map structure.

command-map-spec-registry clj/s

(command-map-spec-registry)

For debugging purposes and some mysterious reason of setting it dynamically during execution

exception-message-header clj/s

execute-config clj/s

(execute-config)

Returns the effective configuration for commando/execute, getting data from dynamic variable commando.impl.utils/*execute-config*

resolvable-fn? clj/s

(resolvable-fn? x)

ResolvableFn clj/s

resolve-fn clj/s

(resolve-fn x)

Normalize x to a function (fn? x) => true.

• Fn((fn [] ..),:keyword)
• Vars(#'clojure.core/str, #'str),
• Symbols('clojure.core/str, 'str)

:clj supports fn?/Var/Symbol (with requiring-resolve fallback). :cljs only accepts actual functions

serialize-exception clj/s

(serialize-exception e)

Serializes errors into data structures.

serialize-exception-fn clj/s≠ multimethod

clj

Multimethod for serializing exceptions to maps. Dispatch based on exception class To add custom serialization for your exception type:

Example (defmethod serialize-exception-fn ClassOfException [e] {:type "my-exception" :message (.getMessage e) ...})

See commando.impl.utils/serialize-exception

cljs

Multimethod for serializing exceptions to maps. dispatch differentiate two type of exception. Not supposed to be extended in cljs

See commando.impl.utils/serialize-exception