docs(): better document ionCanLeave and ionCanEnter

closes https://github.com/driftyco/ionic-site/issues/829

src/navigation/nav-controller.ts

@@ -236,33 +236,69 @@ import { ViewController } from './view-controller';
  *  | `ionViewCanLeave`   | Runs before the view can leave. This can be used as a sort of "guard" in authenticated views where you need to check permissions before the view can leave                                                                                                     |
  *
  *
- * ## Asynchronous Nav Transitions
+ * ## Nav Guards
  *
- * Navigation transitions are asynchronous operations. When a transition is started,
+ * In some cases, a developer should be able to control views leaving and entering. To allow for this, NavController has the `ionViewCanEnter` and `ionViewCanLeave` methods.
- * the `push` or `pop` method will return immediately, before the transition is complete.
+ * Similar to Angular 2 route guards, but are more integrated with NavController. For example, if you wanted to prevent a user from leaving a view:
  *
- * Generally, the developer does not need to be concerned about this. In the event
+ * ```ts
- * multiple transitions need to be synchronized or transition timing is critical,
+ * export class MyClass{
- * the best practice is to chain the transitions together using the return value
+ *  constructor(
- * from the `push` and `pop` methods.
+ *    public navCtrl: NavController
+ *   ){}
  *
- * The `push` and `pop` methods return a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
+ *   pushPage(){
- * Promises are a way to represent and chain together multiple asynchronous
+ *     this.navCtrl.push(DetailPage)
- * operations in order. Navigation actions can be chained together very easily using promises.
+ *      .catch(()=> console.log('should I stay or should I go now'))
+ *   }
  *
- * ```typescript
+ *   ionCanViewLeave(): boolean{
- * let navTransitionPromise = this.navCtrl.push(Page2);
+ *    // here we can either return true or false
- * navTransitionPromise.then(() => {
+ *    // depending on if we want to leave this view
- *   // the transition has completed, so I can push another page now
+ *    if(isValid(randomValue)){
- *   return this.navCtrl.push(Page3);
+ *       return true;
- * }).then(() => {
+ *     } else {
- *   // the second transition has completed, so I can push yet another page
+ *       return false;
-    return this.navCtrl.push(Page4);
+ *     }
- * }).then(() => {
+ *   }
- *   console.log('The transitions are complete!');
+ * }
- * })
  * ```
  *
+ * We need to make sure that or `navCtrl.push` has a catch in order to catch the and handle the error.
+ * If you need to prevent a view from entering, you can do the same thing
+ *
+ * ```ts
+ * export class MyClass{
+ *  constructor(
+ *    public navCtrl: NavController
+ *   ){}
+ *
+ *   pushPage(){
+ *     this.navCtrl.push(DetailPage)
+ *      .catch(()=> console.log('should I stay or should I go now'))
+ *   }
+ *
+ * }
+ *
+ * export class DetailPage(){
+ *   constructor(
+ *     public navCtrl: NavController
+ *   ){}
+ *   ionCanViewEnter(): boolean{
+ *    // here we can either return true or false
+ *    // depending on if we want to leave this view
+ *    if(isValid(randomValue)){
+ *       return true;
+ *     } else {
+ *       return false;
+ *     }
+ *   }
+ * }
+ * ```
+ *
+ * Similar to `ionViewCanLeave` we still need a catch on the original `navCtrl.push` in order to handle it properly.
+ * When handling the back button in the `ion-navbar`, the catch is already taken care of for you by the framework.
+ *
  * ## NavOptions
  *
  * Some methods on `NavController` allow for customizing the current transition.