(descriptor->emap spec api-root)
(descriptor-facts api-root spec-or-specs)
Return a collection of datoms that describe the routes created from the given app spec(s).
Routes are created exactly as in routes
, but are then flattened into
[e a v] triples. Collections of interceptors are represented as if
by a multi-valued attribute on the route entity.
spec-or-specs
is either a single app-spec (as a map) or a
collection of app-specs.
Return a collection of datoms that describe the routes created from the given app spec(s). Routes are created exactly as in `routes`, but are then flattened into [e a v] triples. Collections of interceptors are represented as if by a multi-valued attribute on the route entity. `spec-or-specs` is either a single app-spec (as a map) or a collection of app-specs.
(ensure-schema spec-or-specs)
Given an api-spec or a collection of app-specs, extract the schema norms, ensure they conform, and idempotently transact them into the Datomic DB. Returns a map of {'db-uri' {:connection datomic-conn, :norms {... all merged norms ..}}}.
Given an api-spec or a collection of app-specs, extract the schema norms, ensure they conform, and idempotently transact them into the Datomic DB. Returns a map of {'db-uri' {:connection datomic-conn, :norms {... all merged norms ..}}}.
(expand-api-routes-individually descriptor api-root)
(load-edn-file file-path)
Given a path, loads a descriptor using the proper readers to get support for Vase literals.
Given a path, loads a descriptor using the proper readers to get support for Vase literals.
(load-edn-resource res)
Given a resource name, loads a descriptor or app-spec, using the proper readers to get support for Vase literals.
Given a resource name, loads a descriptor or app-spec, using the proper readers to get support for Vase literals.
(routes api-root spec-or-specs)
Return a seq of route vectors for Pedestal's table routing syntax. Routes
will all begin with api-root/:api-namespace/api-name-tag
.
spec-or-specs
is either a single app-spec (as a map) or a collection of app-specs.
The routes will support all the operations defined in the spec. Callers should treat the format of these routes as opaque. They may change in number, quantity, or layout.
Return a seq of route vectors for Pedestal's table routing syntax. Routes will all begin with `api-root/:api-namespace/api-name-tag`. `spec-or-specs` is either a single app-spec (as a map) or a collection of app-specs. The routes will support all the operations defined in the spec. Callers should treat the format of these routes as opaque. They may change in number, quantity, or layout.
(specs spec-or-specs)
Given a app-spec or collection of app-specs, extract all defined clojure.specs and evaluate them, placing them in clojure.spec's registry.
Given a app-spec or collection of app-specs, extract all defined clojure.specs and evaluate them, placing them in clojure.spec's registry.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close