Giter VIP home page Giter VIP logo

Comments (3)

dmitshur avatar dmitshur commented on July 28, 2024

I receive in the server

As I understand, you have your own GraphQL server where the client is sending the mutation.

I'm not seeing you do anything clearly wrong in the snippet you posted. It looks like it should work.

Are you sure the data in installInfo.Package.Products has non-empty values? Try adding some log statements there to confirm.

The code in graphql package that marshals the variables is very simple:

graphql/graphql.go

Lines 55 to 66 in 3d276b9

in := struct {
Query string `json:"query"`
Variables map[string]interface{} `json:"variables,omitempty"`
}{
Query: query,
Variables: variables,
}
var buf bytes.Buffer
err := json.NewEncoder(&buf).Encode(in)
if err != nil {
return err
}

So it should work. See a demo on the playground: https://play.golang.org/p/LIofG3_Gq1g.

What GraphQL server are you using? Can you dump the raw mutation it receives and see if it looks as expected?

from graphql.

jorgesece avatar jorgesece commented on July 28, 2024

Hi!
I have resolved it by using the json notation, so it passes lowercase variables to the server. I was confused with it because mutation examples do not show how to create the structures for mutation variables.

The solution is to include json:variable

type ProductInput struct {
    Name     graphql.String `json:"name"` 
    Location graphql.String `json:"location"` 
}

Many thanks for you help!

from graphql.

dmitshur avatar dmitshur commented on July 28, 2024

Thanks for following up. I'm glad you got to the bottom of this.

I think I understand what happened now. This general GraphQL client package was factored out of githubql, the GitHub-specific GraphQL client, which I created first. Over there, all the input structs were generated, and they include the json tags. So it's something I completely forgot about that needs to be done in the general case as well.

This is definitely not intuitive, and currently not documented. I should either document this so it's clear this must be done, or improve the graphql code to make it no longer neccessary to manually specify those json tags. They can be inferred from the field name, just need to convert from Go's MixedCaps case to GraphQL's lowerCamelCase (this is already being done for queries, the code for it exists in ident package).

I filed issue 20 for that. Thanks again for the report.

from graphql.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.