Can anyone point me to a reference implementation of nested / namespaced Mutations?
mutation {
Diagnostics {
doSomeAction(input:3){
success
message
}
}
}Presently have single level working just fine (i.e. no Diagnostics in the object above). I can define the schema just fine however run into problems with the sub-mutation actually being resolved.
Hello, Im studying graphql and trying to use it in an existing (huge) project. Have you ever used graphql + clean architeture ? I dont have a lot of experience with graphql, but it seems to go through more than a layer (https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html)
@Nemesisesq I have lots of use cases (business logic layer), its hard for me to connect existing use cases to graphql, for example: if i was using soap/xml and choose to migrate to rest, i'd just update my presenters. its not the case with graphql, its not about just presentation. It doesnt seem to be a good idea to refactor all my application to fit graphql.
You shouldn’t need to do any refactoring
Hi folks! My name is Alison Tai and I’m a program manager at Microsoft. We are looking at how we can improve Azure, and are interested in hearing from you about your API usage. If you are willing, we would greatly appreciate your input on this quick survey: https://aka.ms/AA6378e. Thank you for your time and consideration!
Hello I have a question regarding GraphQL https://stackoverflow.com/questions/59509280/django-graphql-endpoint-testing-unable-to-use-variables-dictionary
const express = require("express");
const { gql, ApolloServer } = require("apollo-server-express");
const heroes = [
{ id: 1000, name: "bunny" },
{ id: 2000, name: "ram" }
];
const typeDefs = gql`
type Query {
heroes: [Hero]
getHero(id: Int): Hero
}
type Hero {
id: Int
name: String
}
`;
const resolvers = {
Query: {
heroes: () => heroes,
getHero: (_, args, context) => heroes.find(e => e === args.id)
}
};
const server = new ApolloServer({ typeDefs, resolvers });
const app = express();
server.applyMiddleware({ app });
app.listen({ port: 4000 }, () =>
console.log("http://localhost:4000" + server.graphqlPath)
);
i have problem in writing the resolver please help me
getHero: (_, args, context) => heroes.find(e => e === args.id)
and my query is
{
getHero(id:1000){
id
name
}
}
and a resolver
export const resolvers = {
User: {
hasLocations(obj, args, context, info) {
// -- count the locations and set to false / true
return true;
}
}
};
any ideea how i could acces the Location query inside my
hasLocation field?
I need a help plz
what do you mean excactlu
Hi
Is there a way to get the query name before it's executed
i'm trying to make a middleware that only lets certain queries go through if not authorized
example :
if currentquery=="login" { //execute the query }
if currentquery=="something else" {
//check the authorization header
then
//execute the query
}
i'm currently doing this in the resolver of each query which is not practical
Is there a way to get the query name before it's executed
i'm trying to make a middleware that only lets certain queries go through if not authorized
example :
if currentquery=="login" { //execute the query }
if currentquery=="something else" {
//check the authorization header
then
//execute the query
}
i'm currently doing this in the resolver of each query which is not practical
I'm having some issues with base64 encoding using the
relay library. I created a SO post here: https://stackoverflow.com/questions/61684910/graphql-go-relay-the-base64-hash-of-my-node-id-is-not-what-i-expect. If anybody can help, would really appreciate it!
we used graphql with wagtail cms django based: https://medium.com/@devs_group/why-our-websites-stay-ahead-c608e3f4bea4
here is the repo
Hi, I'm new to this golang graphql library. I was looking at the concurrent example here.
Why does the library not run the resolvers concurrently by default? If making this behavior the default is a huge breaking change, then perhaps we could add an opt-in wrapper function to the library to enable the feature. Maybe something like this
Why does the library not run the resolvers concurrently by default? If making this behavior the default is a huge breaking change, then perhaps we could add an opt-in wrapper function to the library to enable the feature. Maybe something like this
func AsyncResolve(fn graphql.FieldResolveFn) graphql.FieldResolveFn {
return func(p graphql.ResolveParams) (interface{}, error) {
type result struct {
data interface{}
err error
}
ch := make(chan *result, 1)
go func() {
defer close(ch)
data, err := fn(p)
ch <- &result{data: data, err: err}
}()
return func() (interface{}, error) {
r := <-ch
return r.data, r.err
}, nil
}
}With the above function, you could now easily do stuff like the following:
fields := graphql.Fields{
"hello": &graphql.Field{
Type: graphql.String,
Resolve: AsyncResolve(func(p graphql.ResolveParams) (interface{}, error) {
fmt.Println("hello")
time.Sleep(5 * time.Second)
fmt.Println("hello done")
return "hello", nil
}),
},
"world": &graphql.Field{
Type: graphql.String,
Resolve: AsyncResolve(func(p graphql.ResolveParams) (interface{}, error) {
fmt.Println("world")
time.Sleep(3 * time.Second)
fmt.Println("world done")
return "world", nil
}),
},
}and voila, you've got resolvers that run concurrently :)
I got a mutation which is returning nothing and am wondering how to handle this. I am currently receiving the following error when trying to start the GraphQL server:
fields must be an object with field names as keys or a function which return such an object