This is something that we got wrong on our project initially, then had a guy named Mark come on board and nail a very clean solution.<\/p>\n
What we were trying to accomplish: we wanted to give our Angular Singe Page App some configuration data for initialization. Things like a CSRF token and API URL, so not necessarily things we could load from a web service.<\/p>\n
The wrong way to do it:<\/strong><\/p>\n We started off using an A better way to do it:<\/strong><\/p>\n What we are doing now is putting this in our server-side template:<\/p>\n and then inject the This is something that we got wrong on our project initially, then had a guy named Mark come on board and nail a very clean solution. What we were trying to accomplish: we wanted to give our Angular Singe Page App some configuration data for initialization. Things like a CSRF token and API URL, so … Continue reading Passing configuration to Angular<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[6],"class_list":["post-73","post","type-post","status-publish","format-standard","hentry","category-programming","tag-angular"],"_links":{"self":[{"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/posts\/73","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":3,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/posts\/73\/revisions"}],"predecessor-version":[{"id":95,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/posts\/73\/revisions\/95"}],"wp:attachment":[{"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/media?parent=73"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/categories?post=73"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/george.hotelling.net\/91percent\/wp-json\/wp\/v2\/tags?post=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}ng-init<\/code> on our element. If you RTFM on ng-init<\/code><\/a> they make it very clear that you should not be using it for that purpose. In our defense, the name “init” is right there in the name and the warning wasn’t as bright red in earlier versions of the documentation.<\/p>\n<script>\nangular.module('ns-config', [])\n .constant('config', {{config|js}});\n<\/script>\n<\/code><\/pre>\nns-config<\/code> module into our project. By using Angular’s constant()<\/code> instead of value()<\/code> the config<\/code> object is available in our application’s .config()<\/code> block.<\/p>\n","protected":false},"excerpt":{"rendered":"