This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
Thanks for your input @solussd I'll do some wondering about it.
Just published a new tutorial video (part of a series I'm working on): Untangled/Om Next In The Large. https://youtu.be/j-_itpXEo6w Part 1 covers the very common and popular problem of structuring your app (Union queries, including nesting them), and HTML5 routing (with params). Source code and helper macros included and linked from the video description
@sova i wouldn’t inject anything into the html
you might consider setting a cookie w/ a token and then on app load hitting some /current-user endpoint (authenticated via the token in the cookie)
@sova fwiw, this is what i do. I receive a JWT token on login that i store in localStorage and use on all subsequent requests
Definitely take a look at JWT– it’s a good fit for rich client-side apps as well as native mobile
@danielstockton interesting! thank you both for your recommendations.