literalpie / angular-animate-toolkit Goto Github PK

Ensure that the directive works well alongside other route animations. It's possible it will be a problem because the animation does not play until the component is initialized in the new route.

We also need to make sure the directive excludes itself from any route animations.

There is something wrong with animating elements that have margins. This is probably an say fix - the hard part will be narrowing down which css attribute is wrong.

The service should have a subject that can event emits to indicate that there was movement in the app and elements should re-register their positions.

consumers of the service should be able to subscribe to the observable, as well as trigger the event.

For example, if there is animations between the routes, the event should be triggered after the animations have stopped.

So that multiple elements can have the reposition animations, we need a way of uniquely identifying each element in the service

There are some places where nativeElement is direct manipulated or has attribute values read from it. Renderer2 should be used instead.

I am a terrible person because I do not write tests as I go, but the perfectionist in me (who usually doesn't get much of a say) wants to write tests for this.

use ng-packagr to package the tools as a library that can be published to NPM.

research a way to animate when a list is reordered.

Possibly even when an element is moved for any reason