Support Toastr's newestOnTop config

[bvaughn]

I noticed after switching from pure JS Toastr implementation over to Angular-Toastr that my new toasts were being added to the bottom of the list. This has an unfortunate side effect of making the fade-out look a little jumpy. I thought at first that changing this behavior would just be a matter of changing toastrConfig like...

toastrConfig.newestOnTop = true;

But this didn't seem to have any impact. Next I dug into the source code. Here's the relevant bit of the Toastr source:

function addToast(toast) {
  // Hidden for brevity
if (mergedConfig['newest-on-top'] === true) {
  scope.toasters.unshift(toast);
  // Hidden for brevity
} else {
  scope.toasters.push(toast);
  // Hidden for brevity
}

I'm not sure this is quite so straight forward to implement in your version of Toastr because of how you're using $animate.enter but I think a similar thing could be accomplished by making the following two changes:

Assign a placeholder first child in setContainer

container = angular.element('<div><i></i></div>'); // <i> could be any other inline element

Check toastrConfig and parent the new toast appropriately in _notify

_setContainer(options).then(function() {
  var after = toastrConfig.newestOnTop ? container.find('i') : null; // You could change the default

  $animate.enter(newToast.el, container, after, function() {

Any chance you could make this change?

PS. For what it's worth, I tested this change locally and it seems to work. I'll submit a PR shortly.

[bvaughn]

New PR submitted: #16

[Foxandxss]

That is done now mate.

[bvaughn]

Thanks :)