grasp.core
->>grab-valuecljmacro
(->>grab-value grab-id form)see grab-value docs
see grab-value docs
->grab-valuecljmacro
(->grab-value form grab-id)see grab-value docs
see grab-value docs
current-execution-idclj
emit-grabclj
(emit-grab grab-id form log execution-id)emit-grab-callclj
(emit-grab-call grab-id [f & args :as form] log execution-id)emit-grab-valueclj
(emit-grab-value grab-id form log execution-id)grabcljmacro
(grab form)(grab grab-id form)(grab grab-id form & {:keys [log execution-id]})It chooses if should grab as a call or a value, to see what each does see grab-call and grab-value docs
It chooses if should grab as a call or a value, to see what each does see grab-call and grab-value docs
grab-a-valueclj
(grab-a-value value)grab-callcljmacro
(grab-call form)(grab-call grab-id form)(grab-call grab-id form & {:keys [log execution-id]})Grabs the call and add its execution to the log. It knows how to deal with exceptions, and adds to the log the metadata of the fn being call, the var, the args that were passed as parameter and the result. If it is a pure function (it should) you can replay exactly what happened and than deep dive in that function with more sparse (or not) grabs to pinpoint the problem that you are trying to find. Beside the form you can pass a grab-id as the first parameter, and if you so choose even the atom and execution id atoms, but totally optional and you would be better just using the global ones. Grab-id and execution-id and not that special, are just to help filter the log to find what you want when the log gets chaotic.
Grabs the call and add its execution to the log. It knows how to deal with exceptions, and adds to the log the metadata of the fn being call, the var, the args that were passed as parameter and the result. If it is a pure function (it should) you can replay exactly what happened and than deep dive in that function with more sparse (or not) grabs to pinpoint the problem that you are trying to find. Beside the form you can pass a grab-id as the first parameter, and if you so choose even the atom and execution id atoms, but totally optional and you would be better just using the global ones. Grab-id and execution-id and not that special, are just to help filter the log to find what you want when the log gets chaotic.
grab-valuecljmacro
(grab-value form)(grab-value grab-id form)(grab-value grab-id form & {:keys [log execution-id]})Grabs the value and add it to the log. It knows how to deal with exceptions, and adds to the log the metadata of the fn being call, the var, the args that were passed as parameter and the result. Beside the form you can pass a grab-id as the first parameter, and if you so choose even the atom and execution id atoms, but totally optional and you would be better just using the global ones. Grab-id and execution-id and not that special, are just to help filter the log to find what you want when the log gets chaotic.
Grabs the value and add it to the log. It knows how to deal with exceptions, and adds to the log the metadata of the fn being call, the var, the args that were passed as parameter and the result. Beside the form you can pass a grab-id as the first parameter, and if you so choose even the atom and execution id atoms, but totally optional and you would be better just using the global ones. Grab-id and execution-id and not that special, are just to help filter the log to find what you want when the log gets chaotic.
grabbed-fnclj
(grabbed-fn f)logclj
restart-log!clj
(restart-log!)(restart-log! log)search-for-varclj
(search-for-var p)cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close