This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-20
Channels
- # beginners (43)
- # boot (44)
- # chestnut (17)
- # cider (78)
- # cljs-dev (24)
- # cljsrn (16)
- # clojure (84)
- # clojure-dusseldorf (1)
- # clojure-italy (21)
- # clojure-losangeles (2)
- # clojure-russia (140)
- # clojure-sg (2)
- # clojure-spec (8)
- # clojure-uk (16)
- # clojurescript (23)
- # cursive (7)
- # datascript (1)
- # datomic (18)
- # docker (20)
- # ethereum (1)
- # fulcro (16)
- # garden (4)
- # graphql (27)
- # hoplon (9)
- # jobs (4)
- # luminus (34)
- # off-topic (6)
- # om (4)
- # onyx (35)
- # pedestal (3)
- # re-frame (24)
- # ring-swagger (15)
- # rum (6)
- # shadow-cljs (22)
- # spacemacs (8)
- # specter (22)
- # yada (7)
yeah I’m using that ‘wrapped’ electron app as well. based on what you were saying, checking to see if I missed something on the POST setup. It works fine when I actually POST, but GraphiQL doesn’t grab the schema
@eoliphant are you getting any errors?
ah no at this point, since I’ve got GET enabled it’s all good. I’ll play around with it later to see if I can make the schema show up with post only but for now i’m fine
@eoliphant yeah especially with the entity API 🙂
yeah after I blow through this prototype, I have crazy ideas about doing something like vase, but with GraphQL lol
@eoliphant that’s what I am building right now actually, for a personal project
well, calling my thing “something like vase” would be pretentious; I am trying to develop some way to automate creating graphql APIs on top of datomic
lol. Yeah that’s my starting point as well. Some sort of semi auto mapping from datomic <-> GraphQL etc
What version of Lacinia? This looks like a problem in your schema combined with a bug in Lacinia (for it to get as far as the sanity check: it should produce a useful failure message so you can fix the issue).
And if you could try feeding it into the current version, it might do a better job reporting the problem.
@hlship thank you! I noticed a mistake in my input object (passed as a variable) and correcting it seemed to fix the error
For future reference, could you quickly describe what the function construct-literal-argument
does?