Yes I get that login is not core. My point was regarding the requirement of a login interaction. What was described was setting globals in this interaction. This implies after app bootstrapping. How can you use config in this scenario?
I agree that using a value makes sense, but not in the use case described. Did I misunderstand the request? Raul Sent from my iPhone > On Feb 13, 2014, at 6:48 PM, Martin Alix <[email protected]> wrote: > > Angular does not have a concept of login, that is something you have to > implement yourself... > > .value('config',{}) will be set as soon as the application starts and > available anywhere it is injected. > It just happens to be named config in this example, it could be named > anything, for example .value('foo',{bar:'baz'}) > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
