You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be interesting to create a tool that can walk a selected thread timeline and for each FnCall look up the fn-spec registry, and if any, apply it's :args, :fn and :ret spec to the FnCall args and ret, collecting and listing all failures, and allowing the user to quickly jump to failed spots like we do on the Printer.
This should be pretty straight forward to implement. Fn specs can be retrieved with :
If malli is on the classpath we can also do the same with :
(require '[malli.core :as m])
(m/=> sum [:=> [:cat:int] :int])
;; this can retrieve the schema given the fn ns and name
(get-in (m/function-schemas) '[user sum :schema])
The text was updated successfully, but these errors were encountered:
jpmonettas
changed the title
Spec tool. A tool for leveraging registered function specs.
Spec tool. A tool for leveraging registered functions specs.
Nov 20, 2023
It could be interesting to create a tool that can walk a selected thread timeline and for each FnCall look up the fn-spec registry, and if any, apply it's :args, :fn and :ret spec to the FnCall args and ret, collecting and listing all failures, and allowing the user to quickly jump to failed spots like we do on the Printer.
This should be pretty straight forward to implement. Fn specs can be retrieved with :
If malli is on the classpath we can also do the same with :
The text was updated successfully, but these errors were encountered: