giapnguyen74 / nextql Goto Github PK

I like the idea of GraphQL without the overhead of typing. As Typescript implements definition files, I'm wondering if interfaces can be specified for type checking messages. On both the client and server, the same definition file would be the reference interface.

So NextQL may achieve an opt-in typing safety same as GraphQL, without the overhead or complexity?

Cache computed results is very important. Naturally GraphQL or NextQL resolve values with separate data queries against multi sources. It could return inconsistent results, if backend data changes happened between resolvers executions.
For example:

{
     getPages: {
            content: 1,
            owner: {  // owner is computed from pageId
                      name: 1,
                      avatar: 1
                 }
     }
}

results

{
       getPages: [{
            content: "hello1",
            owner: {
                 name: "giapnh",
                 avatar: "cat"
            }
       }, {
            content: "hello2",
            owner: {
                 name: "giapnh",
                 avatar: "dog"     <- I change my avatar from "cat" to "dog" between nextql query pages.
            }
          
       }]
}

To solve the issue you could use Facebook's dataloader. But I think nextql should able solve the issue, so other nextql-plugins don't need to code their cache solutions.

schema is defined twice for graphql in https://raw.githubusercontent.com/giapnguyen74/nextql/master/images/getdie.png

I really like NextQL.

Am curious; do you have plans to evolve the project?

The NEXT NextQL logo is not centred in its frame and the NEXT in the octagon is also not centred.

Why?
normalizr so popular among GraphQL community because it solve the problem of consume nested data. But it is required you define data schema on client side one more time.

NextQL should support option to return the normalize data instead of nested data.