This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-28
Channels
- # aatree (3)
- # alda (8)
- # avi (21)
- # beginners (37)
- # boot (193)
- # cbus (1)
- # cider (29)
- # cljs-dev (8)
- # cljsjs (3)
- # cljsrn (20)
- # clojure (76)
- # clojure-dev (13)
- # clojure-miami (20)
- # clojure-portugal (2)
- # clojure-russia (220)
- # clojure-sg (2)
- # clojurebridge (5)
- # clojurescript (94)
- # community-development (14)
- # conf-proposals (110)
- # core-async (12)
- # cursive (12)
- # datascript (6)
- # datomic (14)
- # dirac (72)
- # emacs (49)
- # hoplon (86)
- # jobs (33)
- # jobs-discuss (1)
- # ldnclj (6)
- # lein-figwheel (1)
- # off-topic (56)
- # om (139)
- # onyx (29)
- # pedestal (17)
- # proton (23)
- # re-frame (45)
- # reagent (35)
- # ring-swagger (4)
- # test-check (1)
- # testing (8)
- # yada (11)
have a look at the file directory stuff that's behind (yada dir)
the point with sub-resources is that sometimes you don't know up-front what the resource model is - perhaps you don't know until the request is made
the directory contents can change, so you need to wait until the request arrives (I also extract the path-info from the request for this)
different 'types' of files have different possible representations etc.
so if I get it right, the :sub-resource
fn should return a resource model instead of a ring-ish response, right?
@jethroksy: I mean (yada (
, sorry if I am being pedantic and that's what you mean. (yada "/public")
will turn that java.io.String to a handler