Fork me on GitHub

Quick newbie question. Can re-frame-http-fx do cors requests out of the box?


re-frame-http-fx is a thin layer over cljs-ajax, so anything you can do with that you can do with re-frame-http-fx


Hi... Is there a way to change the list of "default" interceptors? other than implementing my own version of reg-event-* ?


From what I see in the code, it's not possible. Is this an intentional decision? Wouldn't it be handy to have a way to configure default interceptors for all handlers?


I think I saw this discussed somewhere, can't remember where though. You can make your own version of reg-event-db and reg-event-fx which have the default interceptors you want, and then use your new version in their place


does anyone have any resources/examples on using core.spec to handle form input validation?


Essentially it comes down to the fact that since it’s so easy to wrap your own to include global interceptors it’s not really worth it making the default behaviour more complicated to achieve a “global” solution.


Well, it's easy if you are starting a new app... For an existing codebase, you have to replace all call-sites. Not the end of the world either... but would be nice for it to be configurable. Thanks!


If you have require’s all over the place for [re-frame.core :as re-frame] since re-frame’s API is pretty small it’s super easy to mask it entirely with a simple wrapper in and then search and replace the original re-frame namespace with [ :as re-frame]