verdnatura-mirror
/
loopback
mirror of https://github.com/strongloop/loopback.git
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release notes

This commit is contained in:
Amir Jafarian 2016-09-30 16:55:46 -04:00
parent 18d9c75abd
commit 1abbbc18e1
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
3.0-RELEASE-NOTES.md
View File

@ -24,7 +24,7 @@ loopback-datasource-juggler from your dependencies.
In version 3.0, we always use bluebird as our promise library In version 3.0, we always use bluebird as our promise library
instead of `global.Promise`. instead of `global.Promise`.
We consider Bluebird API a part of LoopBack API from now on, We consider Bluebird API as part of LoopBack API from now on,
you are welcome to use any Bluebird-specific methods in your applications. you are welcome to use any Bluebird-specific methods in your applications.
If you are using LoopBack with a custom promise implementation provided If you are using LoopBack with a custom promise implementation provided
@ -32,7 +32,7 @@ via `global.Promise`,
you will have to check all places where you are using non-standard promise API you will have to check all places where you are using non-standard promise API
and update them to use Bluebird API instead. and update them to use Bluebird API instead.
Please see [Related code change](https://github.com/strongloop/loopback/pull/1896) here. Please see [related code changes](https://github.com/strongloop/loopback/pull/1896).
## new method of defining remoting metadata ## new method of defining remoting metadata
@ -62,7 +62,7 @@ methods: {
} }
``` ```
Please see [related code change](https://github.com/strongloop/loopback/pull/2174) here. Please see [related code changes](https://github.com/strongloop/loopback/pull/2174).
## remove `Change.handleError` ## remove `Change.handleError`
`Change.handleError` is now removed as it was used inconsistenly for a subset of possible `Change.handleError` is now removed as it was used inconsistenly for a subset of possible
@ -72,7 +72,7 @@ Use PersistedModel to report change-tracking errors via the existing method
PersistedModel.handleChangeError. This method can be customized on a per-model basis to PersistedModel.handleChangeError. This method can be customized on a per-model basis to
provide different error handling. provide different error handling.
Please see [related code change](https://github.com/strongloop/loopback/pull/2308) here. Please see [related code changes](https://github.com/strongloop/loopback/pull/2308).
## remove unused user properties ## remove unused user properties
@ -98,7 +98,7 @@ Developers that are relying on these properties, can redefine them in `user.json
} }
``` ```
Please see [Related code change](https://github.com/strongloop/loopback/pull/2299) here. Please see [related code changes](https://github.com/strongloop/loopback/pull/2299).
## Remove getters for Express 3.x middleware ## Remove getters for Express 3.x middleware
@ -231,4 +231,4 @@ now removed in favor of promoting use of:
- `app.registry.createModel(modelName, properties, options)` to create new model - `app.registry.createModel(modelName, properties, options)` to create new model
- `app.model(modelCtor, config)` to update existing model and attach it to app - `app.model(modelCtor, config)` to update existing model and attach it to app
Please see [related code change](https://github.com/strongloop/loopback/pull/2401) here. Please see [related code changes](https://github.com/strongloop/loopback/pull/2401).