Right - creating a CDTDocumentRevision is broken, which you've mentioned
before.

At this point, we could either document how to use TD* to build a
CDTDocumentRevision, or expand this conflicts v1 work to include the
creation of the CDTMutableDocumentRevision. I prefer the former.

Adam



On Mon, Mar 31, 2014 at 3:09 AM, Mike Rhodes <notifications@github.com>wrote:

> In Classes/common/CDTConflictResolver.h:
>
> > +/**
> > + *
> > + * This method receives the document ID and an NSArray of CDTDocumentRevision
> > + * objects and is intended to be called by CDTDatastore+Conflicts -resolveConflictsForDocument.
> > + * The NSArray includes all conflicting revisions of this document,
> > + * including the current winner, but not in any particular order.
> > + *
> > + * The implementation of this method should examine the conflicts and return
> > + * a winning CDTDocumentRevision object.
> > + *
> > + * When called by CDTDatastore+Conflicts -resolveConflictsForDocument,
> > + * the returned CDTDocumentRevision will be added to the document tree
> > + * as the child of the current winner, and all the other revisions will
> > + * be deleted.
> > + *
> > + * You may also delete the document by setting the CDTDocumentRevision.deleted property.
>
> Not clear where this would be set.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/cloudant/CDTDatastore/pull/22/files#r11109743>
> .
>