This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-24
Channels
- # arachne (3)
- # beginners (39)
- # boot (3)
- # cider (91)
- # cljs-dev (56)
- # cljsrn (4)
- # clojure (267)
- # clojure-dusseldorf (1)
- # clojure-estonia (1)
- # clojure-greece (2)
- # clojure-italy (6)
- # clojure-nl (2)
- # clojure-russia (18)
- # clojure-spec (27)
- # clojure-uk (136)
- # clojurescript (19)
- # core-async (2)
- # cursive (6)
- # datomic (17)
- # emacs (2)
- # fulcro (86)
- # graphql (4)
- # hoplon (13)
- # jobs-discuss (7)
- # jobs-rus (1)
- # keechma (34)
- # keyboards (7)
- # leiningen (5)
- # luminus (4)
- # lumo (8)
- # off-topic (13)
- # om (6)
- # onyx (26)
- # re-frame (22)
- # reagent (1)
- # reitit (2)
- # remote-jobs (8)
- # ring (3)
- # ring-swagger (5)
- # rum (8)
- # shadow-cljs (45)
- # specter (6)
- # unrepl (16)
- # yada (15)
Is there a way to match all “segments” after a certain point as a list param?
e.g. /yada/yada/1.2.10/doc/basics/getting-started/
would have a param :doc ["basics" "getting-started"]
?
I have an endpoint that is returning the same result over and over, but when I run the underlying function (that creates the response for the Yada Resource) in my REPL I get what I expect, a different result time after time.
@martinklepsch bidi has no notion of segments
@maleghast What happens if you curl it?
@dominicm - @mccraigmccraig helped me out - I was being a dumbass in the way I was defining my Yada resource.
Yep - was n00b-ish in the extreme, and if I had really__ been thinking about it I would have spotted it myself.
@dominicm I figured, so what would be a good way of dealing with this?
@martinklepsch each bidi handler can say it matches a path, when asked, whether or not it matches all the remaining path or the start of it
@martinklepsch there is also Yada subresources which you might be looking for?