status-im
/
realm-js
mirror of https://github.com/status-im/realm-js.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove qualification about date precision in API docs

This commit is contained in:
Scott Kyle 2016-05-19 13:33:00 -07:00
parent c947bb946f
commit bd863f7590
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/realm.js
View File

@ -233,8 +233,7 @@ Realm.defaultPath;
* @property {number} "double" - Property may be assigned any number, and will have no loss * @property {number} "double" - Property may be assigned any number, and will have no loss
* of precision. * of precision.
* @property {string} "string" - Property value may be any arbitrary string. * @property {string} "string" - Property value may be any arbitrary string.
* @property {Date} "date" - Property may be assigned any `Date` instance, but will be stored * @property {Date} "date" - Property may be assigned any `Date` instance.
* with second-level precision (a fix for this is in progress).
* @property {ArrayBuffer} "data" - Property may either be assigned an `ArrayBuffer` * @property {ArrayBuffer} "data" - Property may either be assigned an `ArrayBuffer`
* or `ArrayBufferView` (e.g. `DataView`, `Int8Array`, `Float32Array`, etc.) instance, * or `ArrayBufferView` (e.g. `DataView`, `Int8Array`, `Float32Array`, etc.) instance,
* but will always be returned as an `ArrayBuffer`. * but will always be returned as an `ArrayBuffer`.