This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-19
Channels
- # aleph (8)
- # announcements (43)
- # babashka (43)
- # beginners (62)
- # calva (8)
- # cider (27)
- # clj-kondo (18)
- # cljs-dev (25)
- # cljsrn (16)
- # clojure (51)
- # clojure-europe (6)
- # clojure-nl (14)
- # clojure-spec (7)
- # clojure-uk (39)
- # clojurescript (17)
- # cursive (9)
- # datascript (12)
- # datomic (16)
- # events (1)
- # fulcro (7)
- # funcool (1)
- # graalvm (2)
- # graphql (5)
- # jobs (1)
- # juxt (6)
- # kaocha (9)
- # leiningen (11)
- # luminus (1)
- # malli (1)
- # off-topic (80)
- # other-languages (2)
- # overtone (3)
- # pedestal (5)
- # quil (1)
- # re-frame (6)
- # reagent (1)
- # reitit (4)
- # rewrite-clj (5)
- # shadow-cljs (207)
- # spacemacs (1)
- # specter (4)
- # sql (1)
- # vim (14)
- # xtdb (7)
Q: from some failing requests I simply get a 404 back from Lacinia. Is there a good explanation for when this will happen. I see 404 mentioned https://github.com/walmartlabs/lacinia/blob/060cd8c699d07970e96f49b1b15889fef8f17201/docs/tutorial/rating-mutation.rst#id2 but otherise, nothing. I’m sure it’s an error in a resolver but I’d like to know how/why it’s translated to a 404
Nvm. I found the issue. Wasn't lacinia at all, was a broken pedestal route. Occam's razor again
Might be interesting for Lacinia: https://medium.com/@leeb/dataloader-v2-0-925b4dccf8d6