This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-23
Channels
- # admin-announcements (1)
- # alda (1)
- # bangalore-clj (5)
- # beginners (17)
- # boot (392)
- # capetown (4)
- # cider (16)
- # cljs-dev (24)
- # cljsrn (33)
- # clojure (106)
- # clojure-berlin (1)
- # clojure-nl (1)
- # clojure-russia (168)
- # clojure-spec (85)
- # clojure-uk (137)
- # clojurescript (83)
- # clojutre (4)
- # component (10)
- # cursive (6)
- # datavis (9)
- # datomic (11)
- # defnpodcast (15)
- # dirac (4)
- # docker (1)
- # ethereum (1)
- # hoplon (27)
- # jobs (5)
- # jobs-rus (1)
- # lein-figwheel (2)
- # luminus (5)
- # off-topic (5)
- # om (13)
- # onyx (60)
- # parinfer (2)
- # planck (12)
- # proton (2)
- # re-frame (45)
- # rethinkdb (5)
- # ring-swagger (9)
- # spacemacs (9)
- # specter (49)
- # test-check (1)
- # untangled (104)
- # yada (10)
I added yada/uri-for
in one of my resources and now yada/response-for
(which I use for testing) is giving me an error: "Context does not contain a :uri-for entry"
Is there a particular step to generate the :uri-for
field?
@frozenlock Using bidi.vhosts will insert it into the context for you 🙂
dominicm thanks!
@gphilipp: yes, soon after Clojure 1.9 hits
All yada keywords will go into a yada namespace, and this will likely be a yada 1.2 release
I'm very excited to implement bidi with om next, both of them implement server side app handling, I hope to achieve a good experience with both technologies
and yada of course