Merge pull request #94 from strongloop/Link_to_migration_steps

Add link to migration steps

Author: Amir-61

pages/en/lb3/3.0-Release-Notes.md

@@ -28,7 +28,9 @@ We have reworked loopback-datasource-juggler and connectors to not rely on
 a single juggler instance anymore. As the last step, juggler became a regular
 dependency.
 
-See [loopback#275](https://github.com/strongloop/loopback/issues/275).
+Please See [loopback#275](https://github.com/strongloop/loopback/issues/275).
+
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#loopback-datasource-juggler-is-a-regular-dependency-now)
 
 ## Use bluebird as *the* Promise library
 
@@ -37,9 +39,11 @@ instead of `global.Promise`.
 We consider Bluebird API a part of LoopBack API from now on,
 you are welcome to use any Bluebird-specific methods in your applications.
 
-See [loopback#1896](https://github.com/strongloop/loopback/pull/1896) and
+Please See [loopback#1896](https://github.com/strongloop/loopback/pull/1896) and
 [loopback-datasource-juggler#790](https://github.com/strongloop/loopback-datasource-juggler/pull/790).
 
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#no-need-to-polyfill-promise-on-node-v010)
+
 ## Cleanup in conversion and coercion of input arguments
 
 We have significantly reworked conversion and coercion of input arguments
@@ -81,7 +85,7 @@ unaffected. If your start seeing unusual amount of 400 error responses after
 upgrading to LoopBack 3.x, then please check the client code and ensure it
 correctly encodes request parameters.
 
-See the following pull requests for more details:
+Please See the following pull requests for more details:
 
  - [strong-remoting#343](https://github.com/strongloop/strong-remoting/pull/343)
  - [strong-remoting#347](https://github.com/strongloop/strong-remoting/pull/347)
@@ -120,9 +124,11 @@ will need to change implementation accordingly.
 You can learn more about the rationale behind the new handler in
 [this comment](https://github.com/strongloop/loopback/issues/1650#issuecomment-161920555)
 
-See [strong-remoting#302](https://github.com/strongloop/strong-remoting/pull/302)
+Please See [strong-remoting#302](https://github.com/strongloop/strong-remoting/pull/302)
 and [`strong-error-handler`](https://github.com/strongloop/strong-error-handler/).
 
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#new-error-handler-for-rest)
+
 ## Full replace vs. partial update
 
 There are two ways to update an existing record (model instance):
@@ -176,11 +182,13 @@ to simplify the upgrade path:
   allowing applications to opt into the new 3.x behaviour while still
   running on LoopBack 2.x
 
-See [loopback#2316](https://github.com/strongloop/loopback/pull/2316),
+Please See [loopback#2316](https://github.com/strongloop/loopback/pull/2316),
 [loopback-datasource-juggler#788](https://github.com/strongloop/loopback-datasource-juggler/pull/788),
 [replaceOnPUT flag](http://loopback.io/doc/en/lb2/Exposing-models-over-REST.html#replaceonput-flag)
 and related documentation.
 
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#put-methods-perform-full-replace-now)
+
 ## Current context API and middleware were removed
 
 We have removed the following current-context-related APIs:
@@ -198,15 +206,17 @@ on the first HTTP request received:
 ```
 Unhandled error for request GET /api/Users:
 Error: remoting.context option was removed in version 3.0.
-See https://docs.strongloop.com/display/APIC/Using%20current%20context for more
+Please See https://docs.strongloop.com/display/APIC/Using%20current%20context for more
 details.
     at restApiHandler (.../node_modules/loopback/server/middleware/rest.js:44:15)
     at Layer.handle [as handle_request] (.../node_modules/express/lib/router/layer.js:95:5)
 ```
 
-See [loopback#2564](https://github.com/strongloop/loopback/pull/2564)
+Please See [loopback#2564](https://github.com/strongloop/loopback/pull/2564)
 and [documentation](https://docs.strongloop.com/display/APIC/Using+current+context)
 
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#the-current-context-feature-was-moved-to-loopback-context)
+
 ## CORS is no longer enabled
 
 There are two types of applications that are commonly built using LoopBack,
@@ -231,9 +241,11 @@ version of `slc loopback` or `apic loopback`, as these applications don't rely
 on the built-in CORS middleware and configure CORS explicitly
 in `server/middleware.json`.
 
-See [pull request #352](https://github.com/strongloop/strong-remoting/pull/352) and
+Please See [pull request #352](https://github.com/strongloop/strong-remoting/pull/352) and
 [Security considerations](https://docs.strongloop.com/display/public/LB/Security+considerations).
 
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#check-your-cors-configuration)
+
 ## Simpler metadata for remote methods
 
 In 2.x, remote methods were defined as:
@@ -270,7 +282,7 @@ prototype methods (`isStatic: false`).
 }
 ```
 
-See [loopback#2174](https://github.com/strongloop/loopback/pull/2174).
+Please See [loopback#2174](https://github.com/strongloop/loopback/pull/2174).
 
 ## Unused user properties were removed
 
@@ -299,7 +311,7 @@ model json file as follows:
 }
 ```
 
-See [loopback#2299](https://github.com/strongloop/loopback/pull/2299).
+Please See [loopback#2299](https://github.com/strongloop/loopback/pull/2299).
 
 ## Getters for Express 3.x middleware were removed
 
@@ -327,14 +339,16 @@ removed properties together with the middleware module name to use instead:
 
 We have also removed `loopback.mime`, which was always set to `undefined`.
 
-See [loopback#2349](https://github.com/strongloop/loopback/pull/2394).
+Please See [loopback#2349](https://github.com/strongloop/loopback/pull/2394).
 
 ## `loopback.errorhandler` was removed
 
 We have removed `loopback#errorhandler` middleware, users should
 use `strong-error-handler` instead.
 
-See [loopback#2411](https://github.com/strongloop/loopback/pull/2411).
+Please See[loopback#2411](https://github.com/strongloop/loopback/pull/2411).
+
+Please see [how to migrate](http://loopback.io/doc/en/lb3/Migrating-to-3.0.html#new-error-handler-for-rest)
 
 ## Serialization of Date values in responses
 
@@ -368,7 +382,7 @@ regardless of the server timezone settings:
 }
 ```
 
-See [strong-remoting#344](https://github.com/strongloop/strong-remoting/pull/344).
+Please See [strong-remoting#344](https://github.com/strongloop/strong-remoting/pull/344).
 
 ## `PersistedModel.find` provides `ctx.data` in "loaded" hook now
 
@@ -383,7 +397,7 @@ This has been fixed in 3.0 and the "loaded" hook now consistently provides
 checks `if (ctx.instance)` then you can remove this condition together with
 the branch that follows.
 
-See [loopback-datasource-juggler@30283291](https://github.com/strongloop/loopback-datasource-juggler/commit/30283291?w=1).
+Please See [loopback-datasource-juggler@30283291](https://github.com/strongloop/loopback-datasource-juggler/commit/30283291?w=1).
 
 ## `PersistedModel.create` no longer returns the instance(s) created
 
@@ -397,7 +411,7 @@ We have changed the API to be consistent with other DAO methods: when invoked
 with a callback argument, the method does not return anything. When invoked
 without any callback, a promise is returned.
 
-See [loopback-datasource-juggler#918](https://github.com/strongloop/loopback-datasource-juggler/pull/918).
+Please See [loopback-datasource-juggler#918](https://github.com/strongloop/loopback-datasource-juggler/pull/918).
 
 ## Applying an undefined mixin to a LoopBack model throws an error
 
@@ -406,7 +420,7 @@ logged regarding the invalid mixin, which needs to be addressed rather than
 silently ignored. This has been fixed in 3.0, therefore an undefined mixin
 applied to a LoopBack model will throw an error that needs to be handled.
 
-See [loopback-datasource-juggler#944](https://github.com/strongloop/loopback-datasource-juggler/pull/944).
+Please See [loopback-datasource-juggler#944](https://github.com/strongloop/loopback-datasource-juggler/pull/944).
 
 ## Deprecated model events were removed
 
@@ -419,15 +433,15 @@ Model events
   * deletedAll
   * deleted
 
-See [loopback-datasource-juggler#965](https://github.com/strongloop/loopback-datasource-juggler/pull/965).
+Please See [loopback-datasource-juggler#965](https://github.com/strongloop/loopback-datasource-juggler/pull/965).
 
 ## Model property names with dot(s) generates an error
 
 Instead of showing a deprecation warning for model property names with dots,
 for example, `customer.name: 'string'`, an error is thrown in 3.0 for
 enforcing use of valid model property names.
 
-See [loopback-datasource-juggler#947](https://github.com/strongloop/loopback-datasource-juggler/pull/947).
+Please See [loopback-datasource-juggler#947](https://github.com/strongloop/loopback-datasource-juggler/pull/947).
 
 ## Array input for updateOrCreate function is no longer allowed
 
@@ -438,7 +452,7 @@ create new instances with this method before). If you would like to perform a
 bulk `updateOrCreate`, you could use `async.each` or `Promise.all` to
 repeatedly call `updateOfCreate` for each instance.
 
-See [related code change](https://github.com/strongloop/loopback-datasource-juggler/pull/889) here.
+Please See [related code change](https://github.com/strongloop/loopback-datasource-juggler/pull/889) here.
 
 ## Settings `strict: validate` and `strict: throw` were removed
 
@@ -501,7 +515,7 @@ var johndoe = new User({ name: 'John doe', age: 15, gender: 'm'});
     //   Details: gender is not defined in the model (value: 'm').
     ```
 
-See [loopback-datasource-juggler#1084](https://github.com/strongloop/loopback-datasource-juggler/pull/1084).
+Please See [loopback-datasource-juggler#1084](https://github.com/strongloop/loopback-datasource-juggler/pull/1084).
 
 ## Models with auto-generated ids reject user-provided id values
 
@@ -530,7 +544,7 @@ now removed in favor of promoting use of:
 - `app.registry.createModel(modelName, properties, options)` to create new model
 - `app.model(modelCtor, config)` to update existing model and attach it to app
 
-See [loopback#2401](https://github.com/strongloop/loopback/pull/2401).
+Please See [loopback#2401](https://github.com/strongloop/loopback/pull/2401).
 
 ## `Change.handleError` was removed
 
@@ -542,7 +556,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 provide different error handling.
 
-See [loopback#2308](https://github.com/strongloop/loopback/pull/2308).
+Please See [loopback#2308](https://github.com/strongloop/loopback/pull/2308).
 
 ## `loopback.autoAttach` is gone
 
@@ -560,7 +574,7 @@ In LoopBack 3.0, we have removed these two APIs completely.
 `DataSource.registerType()` method was removed as it was a deprecated wrapper
 for `ModelBuilder.registerType()`.
 
-See [loopback-datasource-juggler#976](https://github.com/strongloop/loopback-datasource-juggler/pull/976).
+Please See [loopback-datasource-juggler#976](https://github.com/strongloop/loopback-datasource-juggler/pull/976).
 
 ## strong-remoting API changes
 
@@ -606,7 +620,7 @@ remoteObjectsInstance.defineType(name, converter)
 remoteObjectsInstance.defineObjectType(name, factoryFn)
 ```
 
-See the API docs and
+Please See the API docs and
 [pull request #343](https://github.com/strongloop/strong-remoting/pull/343)
 for more details.