Fields are the data that are sent as part of an event. Events are just maps, where the keys are either keywords or strings and the values may be anything. Since clj-honeycomb wraps the Java Honeycomb SDK, we must transform some of the values from Clojure types into more Java-friendly types where possible.
Only the ->ValueSupplier function in this namespace should be considered part of the public API for clj-honeycomb.
Fields are the data that are sent as part of an event. Events are just maps, where the keys are either keywords or strings and the values may be anything. Since clj-honeycomb wraps the Java Honeycomb SDK, we must transform some of the values from Clojure types into more Java-friendly types where possible. Only the ->ValueSupplier function in this namespace should be considered part of the public API for clj-honeycomb.
(realize m)
Given a map, stringify the keys and realize all the values. This must be done at the last minute before sending an event so that any dynamic/delayed fields are computed as late as possible.
Given a map, stringify the keys and realize all the values. This must be done at the last minute before sending an event so that any dynamic/delayed fields are computed as late as possible.
(separate m)
Given a map, stringify the keys and convert any values that should be ValueSuppliers into them. Then return a tuple where the first item is the submap of the input where no values are ValueSuppliers and the second item is the submap of the input where all the values are ValueSuppliers.
Given a map, stringify the keys and convert any values that should be ValueSuppliers into them. Then return a tuple where the first item is the submap of the input where no values are ValueSuppliers and the second item is the submap of the input where all the values are ValueSuppliers.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close