Liking cljdoc? Tell your friends :D

clojusc.results.errors


any-client-errors?clj

(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.

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.
raw docstring

any-erred?clj

(any-erred? coll)

any-server-errors?clj

(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.

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.
raw docstring

checkclj

(check & msgs)
raw docstring

client-error-codeclj


collectclj

(collect & coll)

default-error-codeclj


erred?clj

(erred? data)
raw docstring

exception-dataclj

(exception-data exception)

get-errorsclj

(get-errors data)

invalid-parameterclj


missing-parametersclj


not-implementedclj


server-error-codeclj


status-codeclj


status-mapclj

This is a lookup data structure for how HTTP status/error codes map to CMR OPeNDAP errors.

This is a lookup data structure for how HTTP status/error codes map to CMR
OPeNDAP errors.
raw docstring

unsupportedclj

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close