Keep ._rev property on returned instance of model about loopback-connector-cloudant HOT 4 CLOSED

@ssh24 What's left for this task:

• Ensure _.rev is not being altered on any of the remaining CRUD methods. The PR in its current state has replaceOrCreate, updateOrCreate and create covered (with tests). You'll probably need to make sure that all of the find and destroy functions also do the same thing.
• You'll also need to demonstrate that they work across the REST APIs; that is, it should show the _.rev property in the returned payloads on GET, and should accept (and use) _.rev on POST/PUT/PATCH/DELETE

With respect to the Swagger/OpenAPI definitions, we can go one of two routes:

1. We inject the _.rev property onto models that use a Cloudant datasource, so that it actually shows up as part of the API def.
2. We document the need to handle _.rev and put the onus on the user/developer to add this property to their model definitions.

from loopback-connector-cloudant.

But considering the nature of Cloudant db, we should ask the caller to provide rev, and return error if it's missing.

A big +1 from me.

I believe the field is called _rev in Cloudant, isn't it? https://docs.cloudant.com/mvcc.html#revisions

I am proposing to define a _rev property on a model at the time when the model is attached to a Cloudant datasource. That way the _rev property will be propagated to Swagger too.

The catch is how to tell clients that _rev should not be included in create requests? This is similar to the problem of excluding id property when forceId is true, see strongloop/loopback#2924

from loopback-connector-cloudant.

@bajtos ah sorry I forgot to direct you to #54 (comment), I made some comment about how to let callers access _rev in that link.

The catch is how to tell clients that _rev should not be included in create requests

True, I will look into this part. My suggestion is based on using an option flag to tell function fromDB() returns _rev with data or not, so doesn't have this concern.

from loopback-connector-cloudant.

The feature has been landed and awaiting to be released on the next major version. Closing this ticket as a result.

from loopback-connector-cloudant.