Hi! I am getting the following error when trying to use an input object as the type of a field in an input object: > Sanity check - no option in construct-literal-argument.

@hlship ^

as per https://github.com/walmartlabs/lacinia/blob/v0.19.0/dev-resources/com/walmartlabs/test_schema.clj#L173 it should work…

Likely a bug. Please add an issue with a minimum example that reproduces the problem.

I am using 0.19.0

It's probably in 0.20.0 as well, but it would be nice to be sure.

I don’t get how that test can pass and not my schema

It’s very simple:

:input-objects
 {:CreateAddressInput
  {:fields
   {:street_name {:type (non-null String)}}}
  :CreateIdentityInput
  {:fields
   {:first_name {:type (non-null String)}
    :last_name {:type (non-null String)}
    :address {:type :CreateAddressInput}}}

i’ll file an issue if I can’t fix it

That sure looks like it should work.

Ah sorry, I am being silly. My field is named street_name in the schema but I was specifying street_address in the variable

Maybe I should file an issue for more specific error message

Problem solved though!

I was thinking that what kind of slack they are talking about in lacinia issues but then realized that it’s probably here 🙂

@hlship btw thanks for accepting my PRs

Thanks for doing the work.

I fixed one issue today related to content-type and made another PR for that too

I'll keep an eye out for it. I'm hoping to get 0.3.0 out soon, but am waiting for other internal devs to review some of the PRs.

https://github.com/walmartlabs/lacinia-pedestal/pull/24 actually it’s this one

I’m already using the master in my own project and thats why I’ll most likely to make new contributions also

at least the react-native apollo implementation is using the utf-8 charset encoded into content-type so it’s good idea to get it out

after that the server implementation should be compatible with all apollo clients