eva.v2.transaction-pipeline.error — com.workiva/eva 2.0.1

Transaction pipeline related errors and error codes.

clock-skew clj macro

(clock-skew detail-str data)

(clock-skew detail-str data cause)

Records this raise-site under :transact-exception/clock-skew in eva.error/eva-error-form, and expands into the equivalent of:

(error :transact-exception/clock-skew (str "excessive transactor clock skew detected: " detail-str) data cause)

error-codes clj

For adding overrides to the types of exceptions thrown from the transactor.

There aren't any as of yet, but it's probably pretty likely we'll find some case of exception that we want to be a bit more obvious from the context of a transaction.

invalid-tx-inst clj macro

(invalid-tx-inst detail-str data)

(invalid-tx-inst detail-str data cause)

Records this raise-site under :transact-exception/invalid-tx-inst in eva.error/eva-error-form, and expands into the equivalent of:

(error :transact-exception/invalid-tx-inst (str "invalid :db/txInstant: " detail-str) data cause)

raise-clock-skew clj macro

(raise-clock-skew detail-str data)

(raise-clock-skew detail-str data cause)

Records this raise-site under :transact-exception/clock-skew in recide, and expands into:

(raise :transact-exception/clock-skew (str "excessive transactor clock skew detected: " detail-str) data cause)

raise-invalid-tx-inst clj macro

(raise-invalid-tx-inst detail-str data)

(raise-invalid-tx-inst detail-str data cause)

Records this raise-site under :transact-exception/invalid-tx-inst in recide, and expands into:

(raise :transact-exception/invalid-tx-inst (str "invalid :db/txInstant: " detail-str) data cause)

raise-tx-fn-error clj macro

(raise-tx-fn-error subtype detail-str data)

(raise-tx-fn-error subtype detail-str data cause)

Records this raise-site under :transaction-pipeline/<subtype> in eva.error/eva-error-form and expands into:

   (raise :transaction-pipeline/<subtype>
          (str "<subtype-generic-str>: " detail-str)
          data
          cause)

The following map shows, for each subtype, what keywords are required in the data map, and what the generic portion of the string will be:

{:tx-fn-threw {:required #{:fn}, :generic-str "A tx-fn threw an exception"}, :tx-fn-illegal-return {:required #{:fn}, :generic-str "A tx-fn return value indecipherable."}}

raise-unrecognized-command clj macro

(raise-unrecognized-command detail-str data)

(raise-unrecognized-command detail-str data cause)

Records this raise-site under :transaction-pipeline/unrecognized-command in recide, and expands into:

    (raise :transaction-pipeline/unrecognized-command
           (str "Cannot interpret object as a transaction command: " detail-str)
           data
           cause)

The following keys are required in the data-map: #{:unrecognized-command}

tx-fn-error clj macro

(tx-fn-error subtype detail-str data)

(tx-fn-error subtype detail-str data cause)

Records this raise-site under :transaction-pipeline/<subtype> in eva.error/eva-error-form, and expands into the equivalent of:

   (error (str "<subtype-generic-str>: " detail-str)
          :transaction-pipeline/<subtype>
          cause)

The following map shows, for each subtype, what keywords are required in the data map, and what the generic portion of the string will be:

{:tx-fn-threw {:required #{:fn}, :generic-str "A tx-fn threw an exception"}, :tx-fn-illegal-return {:required #{:fn}, :generic-str "A tx-fn return value indecipherable."}}

unrecognized-command clj macro

(unrecognized-command detail-str data)

(unrecognized-command detail-str data cause)

Records this raise-site under :transaction-pipeline/unrecognized-command in eva.error/eva-error-form, and expands into the equivalent of:

    (error :transaction-pipeline/unrecognized-command
           (str "Cannot interpret object as a transaction command: " detail-str)
           data
           cause)

The following keys are required in the data-map: #{:unrecognized-command}