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

clojure-to-json clj/s

(clojure-to-json obj entity)

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

datomic-inverse-name clj/s

(datomic-inverse-name rel)

datomic-name clj/s

(datomic-name o)

datomic-schema clj/s

(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/s

(datomic-spec-for-name n)

entities-by-name clj/s≠

clj

(entities-by-name model-path)

cljs

(entities-by-name model-code)

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.

get-minimum-scoping-sets clj/s

(get-minimum-scoping-sets validated-scoping)

Given a validated scoping returns map of sets which has tags as key and each set keeps tags required for scoping that tag

get-scoping-queries clj/s

(get-scoping-queries entities-by-name scoping-defintion push?)

(get-scoping-queries entities-by-name scoping-defintion push? tags)

Takes: entities-by-name, parsed (and validated) EDN of scoping rules, push? config map, with optional keys:

• tags, a set of tags which queries are requested (if not provided all tags are taken by default)
• necessary-tags, a set of tags which are required for scoping selected tags, calculated with tree obtained from scope_dependeny/get-minimum-scoping-sets if not provided queries for all tags will be calculated and result will be filtered according to tags param

A typical invocation looks like this: (get-scoping-queries entities-by-name validated-scope push?))) (get-scoping-queries entities-by-name validated-scope push? {:tags #{:RAEmployee.ofOwner} :necessary-tags #{:RAEmployee.ofOwner :RAOwner.me}}}))) Returns a map with tags and queries generated to obtain entities for indicated user: {:RAEmployee.ofOwner [:find ?RAEmployee-ofOwner :in $ [?user ...] :where [?user :app/uuid ?G__33023] [(= ?G__33024 ?G__33023)] [?RAOwner-me :RAOwner/internalUserId ?G__33024] [?RAEmployee-ofOwner :RAEmployee/owner ?RAOwner-me]]} ...

json-to-clojure clj/s

(json-to-clojure json entity)

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

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

read-pull-scoping-edn clj/s≠

clj

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

cljs

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

Read and validate scoping edn.

reduce-entities clj/s

(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/s

(replace-inverses obj entity)

(replace-inverses obj entity untangle-singles)

scope clj/s

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

(scope config snapshot user entities-by-name scoping-defintion push? tags)

Takes a config map, a snapshot, a user object from DB, entities-by-name and the parsed EDN of rules, push? and optional set of tags to scope. If set of tags to scope is not provided all tags are scoped. A typical invocation looks like this: (scope config (d/db db/conn) user entities-by-name (clojure.edn/read-string (slurp "resources/model/pull-scope.edn")) false) (scope config (d/db db/conn) user entities-by-name (clojure.edn/read-string (slurp "resources/model/pull-scope.edn")) false #{:NOUuser.me :NOLanguage.mine})

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

scope-selected-tags-with-tree clj/s

(scope-selected-tags-with-tree config
                               snapshot
                               user
                               entities-by-name
                               scoping-defintion
                               scoping-sets
                               tags)

Takes: a config map, a snapshot, a user object from DB, entities-by-name, parsed (and validated) EDN of scoping rules, scoping-sets, a map of sets indiacting which tags must be scoped per tag calculated with scope_dependency/get-minimum-scoping-sets tags, set of desired tags.

It is advised to calculacte scoping sets once and pass the result. A typical invocation looks like this: (scope-selected-tags-with-tree config (d/db db/conn) user entities-by-name validated-scope scoping-sets #{:RARestaurant.ofOwner})))

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

spec-for-name clj/s

(spec-for-name n)

special-attribs clj/s

specs clj/s

(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"})}