Skip to content
This repository has been archived by the owner. It is now read-only.

Improve docs on global variables, review best practices #334

Closed
addyosmani opened this issue Mar 24, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@addyosmani
Copy link
Member

commented Mar 24, 2014

Carrying on from #320:

"<app-globals> could wrap the properties in a "globals" object and published it. That would allow you to write: <app-globals id="globals" globals="{{globals}}"></app-globals> and not have to do the business in ready()" from @ebidel

@arthurevans

This comment has been minimized.

Copy link
Contributor

commented Aug 20, 2014

Is this still something we want to do?

@arthurevans arthurevans changed the title Improve docs on global variables Improve docs on global variables, review best practices Oct 10, 2014

@arthurevans

This comment has been minimized.

Copy link
Contributor

commented Oct 10, 2014

We should review best practices with the eng. team, too. Updated title accordingly.

@katejeffreys

This comment has been minimized.

Copy link
Contributor

commented Apr 14, 2017

@addyosmani Is this still a thing? Can the issue be closed?

@katejeffreys

This comment has been minimized.

Copy link
Contributor

commented May 9, 2017

Closing this, as part of my aim to gradually reduce the open issues to a manageable number such that the open issues are meaningful to us. If this is the wrong thing to do, please re-open.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.