I’ve been trying to get the ember-animated-outlet project to work for quite a while, without much luck. All my views are declared explicitly, my main outlet uses the animated-outlet helper and is named “main”, my links are all using link-to-animated (with animations defined), and all programatic transitions are made using transitionToAnimated(name, animations, model).
It is working for all top level routes, however, it doesn’t work for any of the child routes. When programmatically making the transition with transitionToAnimated() called inside of an action handler in the application route, the transition is only partially made. The url displays the correct url of that child route, but the view and all html inside its template is not being rendered.
My code for the parent transition (that works) and the child (that doesn’t work):
In the action handler for transitioning to the child (which isn’t working) I know that the action is being called, the route name is correct, the main animated outlet is in fact named “main”, and that the group model is defined.
I am trying to render both the parent and the child route into the same outlet per the source for the ember-animated-outlet demo on github (lines 26 and 29). One of the problems I’ve observed is that the views are not being displayed in the view tree in the ember inspector.
So I got liquid fire working extremely easily with a new instance of ember using cli, however in a more complicated instance that uses a rails backend I’ve been having some trouble.
I get two errors after changing the outlet in my application template to:
{{liquid-outlet use="crossFade"}}
The errors are (the second only occurs when specifying the “use”):
Awesome, thanks for the help. The problem I was experiencing before though was that after I installed velocity.js (which I know was successfully included) and the latest liquid-fire script (v0.5.0), I got this error:
Uncaught TypeError: Cannot read property 'RSVP' of undefined
Which came from the liquid-fire script itself on line 423. I’m going to install an older version of liquid-fire to see if its a bug, but besides that, do you see any way to deal with this error?