Add import information

[b264]

Cannot use ToastController without knowing from where to import it

Short description of what this resolves:

The doc is incomplete because this code won't work without first importing the class. This is a common occurrence across virtually all of the Ionic docs. This is the one that got me today, so I thought I'd fix it.

Changes proposed in this pull request:

• add import to code example in doc

[b264]

I had to find this offsite on https://alligator.io/ionic/toast-controller-ionic/

[AmitMY]

Thanks for this PR.
I don't believe this is really needed, as all of the imports are from ionic-angular.
Plus, most IDEs can auto import.

However, if you find this really needed, and a core member gives a green light for merging, this should be more complete, so it is needed in all components.

[brandyscarney]

Thanks for the PR! @mhartington what do you think of adding the package name to the top of API docs, similar to how Angular does it: https://angular.io/api/common/isPlatformBrowser

It would be helpful for quickly differentiating between the Native API as well: http://ionicframework.com/docs/native/action-sheet/

[mhartington]

This can be done. While this is pretty obvious to us (since we in the code day to day), it's helpful to have.

We could just add a sample import statement if that helps? Feel like thats a bit more useful than what the angular docs provide

[mhartington]

Oh, and yeah, this looks good to merge

[brandyscarney]

@mhartington I mostly meant some sort of sample import or reference to which package it comes from at the top of the API docs. The usage example is great too but it would be something that the user immediately sees when they visit each API doc. Something we could add to dgeni.