Compare commits

..

2 Commits

Author SHA1 Message Date
138290a7b8 1.0.13 2016-09-13 10:23:49 +02:00
036cafc282 improve README 2016-09-13 10:23:46 +02:00
2 changed files with 11 additions and 4 deletions

View File

@ -72,11 +72,18 @@ DbDoc extends your class with the following methods:
that extends DbDoc as well and call .saveDeep() on them as well. that extends DbDoc as well and call .saveDeep() on them as well.
Loops are prevented Loops are prevented
So now we can get store instances of classes to Db... So now we can **store** instances of classes to Db...
How do we get a new class instances from a Doc in DB? How do we **get** a new class instance from a Doc in the DB?
Easy! Take a look at the constructor. When you specify `optionsArg.queryArg` Easy! Take a look at the constructor. When you specify `optionsArg.queryArg`
smartdata will fill in the data from the database! smartdata will fill in the data from the database!
But when you specify a `optionsArg.dataArg` instead But when you specify a `optionsArg.dataArg` instead
the data is for the class is taken from there :) the data for the class is taken from there :)
## TypeScript
How does TypeScript play into this?
Since you define your classes in TapeScript and types flow through smartdata in a generic way
you should get all the Intellisense and type checking you love when using smartdata.
smartdata itself also bundles typings.
So you don't need to install any additional types whenimporting smartdata.
[![npm](https://push.rocks/assets/repo-header.svg)](https://push.rocks) [![npm](https://push.rocks/assets/repo-header.svg)](https://push.rocks)

View File

@ -1,6 +1,6 @@
{ {
"name": "smartdata", "name": "smartdata",
"version": "1.0.12", "version": "1.0.13",
"description": "do more with data", "description": "do more with data",
"main": "dist/index.js", "main": "dist/index.js",
"typings": "dist/index.d.ts", "typings": "dist/index.d.ts",