Including CSRF_TOKEN when using lineman about end-to-end-with-angularjs HOT 7 CLOSED

Hey @sdeering, I've used the following technique to achieve what you're talking about:

https://gist.github.com/davemo/6141699

from end-to-end-with-angularjs.

Keep in mind you will need to setup your angular app to manual bootstrap using this approach. https://docs.angularjs.org/api/ng/function/angular.bootstrap

from end-to-end-with-angularjs.

Thanks @davemo, so there isn't a way you thought of to avoid that extra HTTP request?

from end-to-end-with-angularjs.

Inlining the value in a server-side template would be the only way to avoid that request @sdeering :)

from end-to-end-with-angularjs.

Just did a quick blog post on this. @davemo keen to hear what you think mate. http://angularjs4u.com/concepts/laravel-4-angularjs-architecture/

from end-to-end-with-angularjs.

Nice work @sdeering! I just read your post; how you handled the CSRF_TOKEN between dev/prod makes sense, it's basically the same split of client/server assets. Injecting the meta tag for your prod build is a nice way to handle avoiding that HTTP request for the token. I'm curious though, the post didn't go into detail on how you configured bootstrapping to be manual with the requested token vs automatic with the injected token. How are you achieving that part of the setup?

from end-to-end-with-angularjs.

Thanks @davemo yeah for that bit I just checked to see if the meta tag exists. https://gist.github.com/sdeering/4356baed3692d26ab778

from end-to-end-with-angularjs.