Design pattern for sitewide configuration in Angular JS

Question

I want to set some user preferences in my angular app. I will get these preference from a REST api so I will need to make a http call. Once these have been fetched from the API, their values will not be modified.

What is the best practice in this case?

Can I make http calls in angular.module.value? Or use something like a provider? Or just write a service? What are the things to consider in any of these approaches?

What is the design pattern to be followed in this case?

Important question here is when gyou will use these preference, during the angular app bootstrap process? — Satpal
– Satpal, Commented Oct 20, 2017 at 7:28

Chris Halcrow · Accepted Answer · 2017-10-20 07:26:20Z

1

You could create a service using the factory recipe. That will make the code a lttle cleaner and more modular.

Following that, you could put the user preferences on the $rootScope. This is a good case for a valid use of $rootScope, since your values are constants with application-wide applicability.

answered Oct 20, 2017 at 7:26

Chris Halcrow

32.5k19 gold badges202 silver badges235 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

maddie Over a year ago

Thank you. I will give this a try.

Collectives™ on Stack Overflow

Design pattern for sitewide configuration in Angular JS

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related