lambdaconnect-model.core — io.spinney/lambdaconnect-model 1.0.4

clojure-to-json clj

(clojure-to-json obj entity)

(clojure-to-json obj
                 entity
                 inverse-parser-for-attribute
                 inverse-parser-for-relationship)

datomic-inverse-name clj

(datomic-inverse-name rel)

datomic-name clj

(datomic-name o)

datomic-schema clj

(datomic-schema entities-by-name)

Automatically generates schema for the Core Data xml model file the path was provided to.

datomic-spec-for-name clj

(datomic-spec-for-name n)

entities-by-name clj

(entities-by-name model-path)

Generates a dictionary keyed with entity names and valued in entity representations for a given core data model file. These include names, attributes and relationships. See core-data-xml module for details on the data model used.

json-to-clojure clj

(json-to-clojure json entity)

Converts json-based map into the one that conforms to the spec.

read-pull-scoping-edn clj

(read-pull-scoping-edn path entities-by-name)

Read and validate scoping edn.

reduce-entities clj

(reduce-entities scoped-entities)

Takes what 'scope' produces and aggregates all the entity types (so :NOUser.me and :NOUser.peer become :NOUser with unified ids)

replace-inverses clj

(replace-inverses obj entity)

(replace-inverses obj entity untangle-singles)

scope clj

(scope config snapshot user entities-by-name edn push?)

Takes a snapshot, a user object from DB, entities-by-name and the parsed EDN of rules. A typical invocation looks like this: (scope (d/db db/conn) user entities-by-name pull-scoping-edn)

Returns a map with db ids, something like: {:FIUser.me #{11122, 1222} :user #{2312312}}

spec-for-name clj

(spec-for-name n)

special-attribs clj

specs clj

(specs entities-by-name)

(specs entities-by-name generators)

Define the specs for all the entities. The specs relate to the entities by their unqualified namespaced names, e.g. ':lambdaconnect-model.spec.json/FIUser' for the user in jsons and ':lambdaconnect-model.spec.datomic/FIUser' for the user saved to database

The generators table lists custom generators and is optional. For example: {:FIUser/gender #(s/gen #{"U", "M", "F"})}