Schema API improvements #8

createEntity

• allow to created nested entities
• allow to created nested entities (recursively)
• typing for creating nested entities
• typing for creating nested entities (recursively)
• schema validation for nested entities?
• relations should be defined on both end
• decide and implement how relations are stored
• allow to provide IDs for relations ["abc", "def"]
• allow to mix objects and IDs for relations ["abc", { id: "def", name: "lala" }] (if id: def exists it's an upsert for the attributes that are included)
• make all fields optional
• add implicit entity properties (e.g. name, description, cover)
• make sure to only return get fields which are defined in the query

useQuery

• resolve nested entities
• resolve nested entities (recursively)
• typing for nested entities
• typing for nested entities (recursively)
• filters for text, number, checkbox
• reverse relationship queries?
• make all fields optional
• always include the id and types
• return array instead of object
• handle circular dependencies
• add implicit entity properties (e.g. name, description, cover)

getById

• implement

updateEntity

• implement

deleteEntity

• implement

setTriple

• define API