v0.21.3

to support npm publish, removing npm audit as a step until npm/npm#20564 is resolved

v0.21.2

See Milestone v0.21.2

v0.21.1

See Milestone v0.21.1

Bug Fixes

#255 & #256

Special thanks to @CarsonF!

v0.21.0

See milestone Milestone 0.21.0

What's new

See #252 -- introduced an event emitter for when Sakuraapi.listen and close get called... in case you need that sorta thing.

0.20.1

See Milestone 0.20.1

Bug Fix / Breaking Change

#249 projection bug fix; projection inclusion / exclusion works independently at each model when dealing with sub-documents. For example, the projection for a parent can be inclusive and the projection for the child can be exclusive.

{
    id: 0,
    child: 1
}

or:

{
    id: 0,
    child: { name: 1 }
}

0.20.0

See Milestone 0.20.0

Bug Fixes

#242 - if a sub document has an @Id field, fromDb will properly populate that field if there's a _id field in the DBO. In order to refactor the fromDb operator to be easier to maintain in the future, promiscuous mode no longer cascades from the a parent model to child models. Also, defining promiscuous mode in the dbConfig preferences of @Model is now deprecated and will be removed in the future. For now on, define promiscuous mode like this:

@Model({promiscuous: true})
class SomeModel ... etc

#243 - you can now assign a default value to an @Id decorated field in a sub document and it will properly map to and from _id. For example:

    describe('#243 @Id fields should map to _id in dbo', () => {

      @Model()
      class Child extends SapiModelMixin() {
        @Id()
        id: ObjectID = new ObjectID();
      }

      @Model({
        dbConfig: {
          collection: 'users',
          db: 'userDb'
        }
      })
      class Parent extends SapiModelMixin() {
        @Id()
        id: ObjectID = new ObjectID();

        @Db({model: Child})
        children: Child[];
      }

      it('toDb', async () => {

        const parent = new Parent();
        parent.children = [
          new Child(),
          new Child()
        ];

        const result = parent.toDb();

        expect(ObjectID.isValid(result._id)).toBeTruthy();
        expect(ObjectID.isValid(result.children[0]._id)).toBeTruthy();
        expect(ObjectID.isValid(result.children[1]._id)).toBeTruthy();

      });
    });

Breaking Changes

See notes above on #242. This is being done on an ultra-minor version because as far as I'm aware, no project is using the promiscuous mode feature with sub-documents such that the cascading behavior was expected.

There were many cases where model.toJson() would marshall properties without @Json operators to a JSON dto. That is no longer the case. You need to explicitly decorate fields with @Json if you want them to be marshalled to a JSON dto.

Worth Noting

#246 injects useNewUrlParser=true into your MongoDB options.

Core Developers

If you work on SakuraApi core, and you use Webstorm, the .idea config now includes a setup for using Webstorm's debugger.

0.19.5

See Milestone 0.19.5

What's new

#239 MongoDB and Express are now peer dependencies.

0.19.4

See Milestone 0.19.4

Dependency Updates

#237 updates, npm audit fixes, etc.

0.19.3

See Milestone 0.19.3
On the hunt for a mongodb problem that's impacting some production systems running SakuraApi.

Thanks to @candleshine for the research and the work. Thanks also to Uma. See: https://jira.mongodb.org/browse/NODE-1637

Bug Fix

#235 removes dependency that was overriding actual dependency that's wanted.

0.19.2

See Milestone 0.19.2

Welcome @RobbSadler as a contributor

Bug Fix

#233 resolves issue where sub documents were being contaminated by prior sub-documents when fields were not set.