You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many organizations centralize around one or more types of document, or data, but need the ability to monitor edits on a field-by-field basis. Similar to a CRM with customizable contacts, we should include a mechanism for storing documents of multiple types and tracking their changes.
Proposed schema
id uuid
type string (use ObjectType enum to validate type)
Many organizations centralize around one or more types of document, or data, but need the ability to monitor edits on a field-by-field basis. Similar to a CRM with customizable contacts, we should include a mechanism for storing documents of multiple types and tracking their changes.
Proposed schema
uuid
string
(useObjectType
enum to validate type){[key: string]: {[key: string]: any} }
any
Array<{[key: string]: any}>
(todo: define PropertyHistory and Property interfaces)any
any
string
number
(UTC unix time with millis)string
(ISO-8601)string
(ISO-8601)boolean
integer
TODO: consider group and user ownership (use graph or just FK columns within: KISS)
Other consideration
Schema
entity store to validate dynamic node typesclass-validator
The text was updated successfully, but these errors were encountered: