Fork me on GitHub
#graphql
<
2017-09-20
>
eoliphant14:09:40

Hey @hmaurer wiring up the GET seems to have fixed ti

eoliphant14:09:04

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

hmaurer14:09:50

@eoliphant are you getting any errors?

eoliphant14:09:49

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

eoliphant14:09:13

this is really cool stuff, i’m using it with datomic. they really go together well

hmaurer14:09:22

@eoliphant yeah especially with the entity API 🙂

eoliphant14:09:44

yeah after I blow through this prototype, I have crazy ideas about doing something like vase, but with GraphQL lol

hmaurer15:09:56

@eoliphant that’s what I am building right now actually, for a personal project

hmaurer15:09:27

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

eoliphant15:09:04

lol. Yeah that’s my starting point as well. Some sort of semi auto mapping from datomic <-> GraphQL etc

stijn18:09:24

i'm doing more or less the same for a project we're working on 🙂

hmaurer19:09:34

@stijn could you elaborate a bit? it would be nice to share ideas

hmaurer23:09:53

@hlship Hi! I am getting an error with Lacinia which is a bit confusing me

hmaurer23:09:55

> Sanity check - no option in construct-literal-argument

hmaurer23:09:24

Do you know where it could be coming from?

hlship23:09:11

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).

hlship23:09:37

That's ancient by my standards. 🙂

hlship23:09:00

Do you want to DM the schema, I'll see if anything jumps out.

hlship23:09:35

And if you could try feeding it into the current version, it might do a better job reporting the problem.

hmaurer23:09:49

@hlship thank you! I noticed a mistake in my input object (passed as a variable) and correcting it seemed to fix the error

hmaurer23:09:59

I’ll upgrade Lacinia to get the latest error messages!

hmaurer23:09:51

For future reference, could you quickly describe what the function construct-literal-argument does?

hmaurer23:09:05

well, not exactly what it does, but what its purpose is

hlship23:09:25

It reformulates an field argument value provided as a variable so that it appears as if parsed from a GraphQL query, with checks along the way, and scalar conversions.