-
Notifications
You must be signed in to change notification settings - Fork 11
Versioning #235
Copy link
Copy link
Open
Labels
apiImproves the APIImproves the APIfeaturepackage:corecore packagecore packagepackage:crdtscrdts packagecrdts package
Metadata
Metadata
Assignees
Labels
apiImproves the APIImproves the APIfeaturepackage:corecore packagecore packagepackage:crdtscrdts packagecrdts package
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a big problem space, but we can try to support at least a little.
For now,
CObjecttreats children like protobuf optional values, i.e., it doesn't complain if it gets a message/savedState for a child it doesn't have. This allows protobuf-style versioning (add and delete CObject children, so long as names stay fixed over time). However, we need to document this.Is that sufficient for real apps? Or do we need something more Cambria-style?