Is there a way to modify the way figwheel serves up the application? I have the :ring-handler
option set, for example, but the initial loading of the app seems to always load up the index.html
file directly...reason I ask is I'm trying to inject a CSRF token into the page, and can't get figwheel to run my "/"
route on load...
Ah...maybe I'm misunderstanding how figwheel works. I'm using chestnut, which launches figwheel at port 3449, but also a Jetty server at port 10555. It appears that I can actually navigate directly to my server at 10555 and still get all the benefits of fighweel hot-loading, and can easily inject the CSRF token now...is this a valid way to use figwheel, or am I missing something?