This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-01
Channels
- # announcements (3)
- # babashka (17)
- # beginners (163)
- # bristol-clojurians (1)
- # calva (18)
- # chlorine-clover (17)
- # clj-kondo (13)
- # cljs-dev (50)
- # cljsjs (3)
- # cljsrn (13)
- # clojure (218)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (10)
- # clojure-nl (8)
- # clojure-uk (107)
- # clojurescript (25)
- # conjure (163)
- # cursive (63)
- # data-science (9)
- # datomic (38)
- # docker (1)
- # figwheel (34)
- # figwheel-main (3)
- # fulcro (15)
- # graalvm (1)
- # helix (12)
- # jobs (3)
- # juxt (5)
- # kaocha (3)
- # lein-figwheel (2)
- # leiningen (6)
- # luminus (2)
- # malli (1)
- # meander (12)
- # nrepl (4)
- # rdf (2)
- # re-frame (2)
- # reagent (7)
- # reitit (5)
- # remote-jobs (2)
- # rum (1)
- # shadow-cljs (65)
- # spacemacs (27)
- # tools-deps (18)
- # vim (19)
- # xtdb (2)
is there a way of not throwing errors in case the response dont match the spec in the :body
clause?
for me a log message would be enough, If dont for an endpoint to fail because I didnt anticipated some key
it would be nice to have a way to set the preferred behaviour, in development I think this feature is cool but I dont want to be that strict in production
Hi. I wonder if anyone can help me. I have the following route /sdmxapi/rest/data/{flow-ref}/{key}/{provider-ref}
, but the following request URL http://localhost:3030/sdmxapi/rest/data/SARB.ERD%2CTEST%2C1.0/./SARB.ERD%2CTEST returns 404 not found
. This is due to {key}=.
, this is also the case for {key}=..
, but not for {key}=...
. Three or more periods work just fine. Anybody know why this is?
I think it may have to do with the single dot referring to the "current" directory and the double dot referring to the parent directory.
I see that http://localhost:3030/sdmxapi/rest/data/SARB.ERD%2CTEST%2C1.0/../SARB.ERD%2CTEST resolves to http://localhost:3030/sdmxapi/rest/data/SARB.ERD%2CTEST, which explains the 404.