This repository is meant to bring together methods and functions for doctypes that are shared across several applications.
The Document API is useful when you need to have global models, available across files.
It can be used as a base for other document types (see BankTransaction for example).
In the following section, we will see how to deal with a fictitious io.cozy.simpsons
doctype (we are developing a konnector to retrieve al the Simpson characters). First, let's create a class Simpson
that inherits from Document
:
const { Document } = require('cozy-doctypes')
class Simpson extends Document {}
Second, let's specify the doctype:
const { Document } = require('cozy-doctypes')
class Simpson extends Document {}
Simpson.doctype = 'io.cozy.simpsons'
Then we provide a cozy-client-js
instance to our class. We are going to use cozy-konnector-libs to get this instance. Take a look at the konnectors documentation to learn more about that.
const { Document } = require('cozy-doctypes')
const { cozyClient } = require('cozy-konnector-libs')
class Simpson extends Document {}
Simpson.doctype = 'io.cozy.simpsons'
Simpson.registerClient(cozyClient)
With this, the class is already usable. For example, we can create a new document:
Simpson.create({
name: 'Homer'
})
Or get some documents given their ids:
const documents = await Simpson.getAll(['id1', 'id2', 'id3']
Take a look at the Document class to see all the methods it implements.
There are some properties that can be given to Document
that have a special meaning.
idAttributes
is an array of attributes that are seen as ids. When Document
knows that, it becomes able to determine if a given document must be created or updated. This is used in the createOrUpdate
method. Let's say that we want the name
of our Simpson
s to be an id:
Simpson.idAttributes = ['name']
Now, if we do the following:
Simpson.createOrUpdate({ name: 'Homer', description: 'Likes donuts' })
Since we said that name
is an id attribute, the document we previously created with the name « Homer » will be updated. But if we do:
Simpson.createOrUpdate({ name: 'Marge', description: "Homer's wife" })
This document will be created, because no document exists with this name
.
checkedAttributes
is an array of attributes. But it is used to determine if a document should be updated or not. Let's say that we want a document to be updated only if its description
changed:
Simpson.checkedAttributes = ['description']
Now, if we try to update a document, without changing its description
:
Simpson.createOrUpdate({ name: 'Marge', children: ['Bart', 'Lisa', 'Maggie'] })
Then it will not be updated, even if we specified a new children
attribute.
createdByApp
is the slug of an application / konnector that creates the document. This information is used for cozy metadatas (see the metadatas documentation to learn more). If we provide this, the metadata is automatically added to any created or updated document:
Simpson.createdByApp = 'my-awesome-simpsons-konnector'
Simpson.createOrUpdate({ name: 'Bart' })
The created document will have a cozyMetadata
property like this:
{
"_id": "the_id_generated_by_couchdb",
"name": "Bart",
"cozyMetadata": {
"createdByApp": "my-awesome-simpsons-konnector"
}
}
The package.json
has both main
and browser
fields. This allows
-
a nodeJS runtime to run the non transpiled code (async/await are for example supported in nodeJS) which allows for easier to read stacktraces.
-
browser runtimes to use transpiled code
The only caveat here is that we must pay attention to features that we use that are not supported yet in nodeJS, for example
- the lack of ES6 module support in nodeJS, we have to use
module.exports
- class properties: must bind the methods in the constructor
webpack doc for browser field: https://webpack.js.org/configuration/resolve/#resolvealiasfields
package.json doc for browser field: https://docs.npmjs.com/files/package.json#browser