Skip to content

Conversation

@barbatus
Copy link
Contributor

After having tested my app, I decided that recent changes to the onAfterAction are too complex.
I propose to revert it back with once change: check it's been compiled only once. It's what regular Angular needs. Anything else is up to a developer. For example, one could create a separate Angular module with onAfterAction (or whatever) and write there any route changes handling (as I did).

@Urigo
Copy link
Owner

Urigo commented Apr 23, 2015

@barbatus you are the iron:route boss :)

Urigo added a commit that referenced this pull request Apr 23, 2015
Reverts back recent changes to the onAfterAction handler.
@Urigo Urigo merged commit c4e8c8f into Urigo:master Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants