-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added additional docs for htmlReady() function #13
Conversation
…lReady() function on the config level, without having to implement it for each controller seperately
Ah! Didn't see that. Let me take a look. |
While it's a nice addition, I guess we should leave the developer the burden of knowing when its view is finally rendered. |
You are probably right. I guess then I'll bring back the timeout outside of the removed event, On Wed, Oct 30, 2013 at 7:17 PM, Steeve Morin notifications@github.comwrote:
|
That said, it's a neat trick, so I'm for documenting it. |
There we go, I've added one commit to each of my pull requests, please take On Wed, Oct 30, 2013 at 7:21 PM, Steeve Morin notifications@github.comwrote:
|
Added additional docs for htmlReady() function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
l
With a suggestion on how to implement the call of this function within the config function of the Angular app, this way it automatically applies to the entire application without a need for specific implementation in every view, and without breaking your head with counting ajax requests or anything else if you're running a heave AJAX application such as I do.