cmr.exchange.common.results.errors
Documentation forthcoming
any-client-errors?
(any-client-errors? errors)(any-client-errors? errors-map errors)In arity-1, expections a map of the form {:errors [...]}. In arity-2, the first parameter is a status map with keys being error codes and values being the error messages associated with those codes.
any-erred?
(any-erred? coll)Documentation forthcoming
any-server-errors?
(any-server-errors? errors)(any-server-errors? errors-map errors)In arity-1, expections a map of the form {:errors [...]}. In arity-2, the first parameter is a status map with keys being error codes and values being the error messages associated with those codes.
check
(check & msgs)client-error-code
Documentation forthcoming
collect
(collect & coll)Documentation forthcoming
default-error-code
Documentation forthcoming
erred?
(erred? data)exception-data
(exception-data exception)Documentation forthcoming
get-errors
(get-errors data)Documentation forthcoming
invalid-parameter
Documentation forthcoming
missing-parameters
Documentation forthcoming
not-implemented
Documentation forthcoming
server-error-code
Documentation forthcoming
status-code
Documentation forthcoming
status-map
This is a lookup data structure for how HTTP status/error codes map to CMR OPeNDAP errors.
unsupported
Documentation forthcoming