Questions
-
How to fix error output format in Nest.js + graphql?
0 Faced the problem of getting errors from graphql in nest.js when the data does not pass validation. I wrote a global filter to bring it all to a single format, but it doesn’t want to work, or rather it works, but graphql wraps everything in a bunch of data and originalError GraphQLModule.forRoot<ApolloDriverConfig>({ driver: ApolloDriver, […]
-
user match query does not exist
0 I have been tasked to create separate user model for third_party users who are to access our endpoint so i created separate user named ApiCliet and inherited the Abstract user model of Django i also created a custom authentication for that user model only and then crated two mutation to create an api client […]
-
Graphql ID resolves as string even if it’s integer
1 I’m new to graphql and hope someone can explain me this ID type that is always string. As said in the docs: The ID scalar type represents a unique identifier, often used to re-fetch an object or as a key for a cache. If you use, for example, some caching client like Apollo, each […]
-
C++20 use concept to restrict an ‘auto’ non-type template argument?
9 I have a template class taking several non-type arguments (GPIO descriptors). Auto is used to allow several different GPIO implementations to be used. These implementations can’t derive from a common base class. Can I use a concept to restrict these arguments to ones with the right interface? I got a concept but it’s not […]
-
SpringBoot graphQL getting Invalid Syntax for nested Object
0 I am using GraphQL in my SpringBoot app. While the CRUD operations are running for single objects, I am facing the issue of Invalid Syntax for nested objects. Please find the code below and suggest. graphql type Book { isn: Int title: String author: String publishedDate: String publisher: Publisher! } input PublisherInput { pId […]
-
How can I implement a HotChocolate FieldResolver when the resolved value depends on another field?
0 I have the following code designed to apply a list of errors to resolved items by fetching the full list of errors from another service which that caches them for performance reasons: public class MyEntityExtensions : ObjectType<MyEntity> { protected override void Configure(IObjectTypeDescriptor<MyEntity> descriptor) { descriptor .Field("errors") .Type(typeof(List<Error>)) .Resolve(async context => { var errorCache = […]
-
Graphql mutation error: “Field ‘createUser’ is missing required arguments: input”
7 I’m trying to follow along this article on how to create a mutation on a rails server using GraphQl https://www.howtographql.com/graphql-ruby/4-authentication However, I’m stuck at the CreateUser Mutation step, I get the follow error hash when trying it out in GraphiQL: { “errors”: [ { “message”: “Field ‘createUser’ is missing required arguments: input”, “locations”: [ […]
-
Apollo Client: switch between local and remote server
0 Currently I’m creating an http link with a relative URI. This works when the server is running locally, and also works when the client and server are hosted remotely: const httpLink = createHttpLink({ uri: ‘/.netlify/functions/foo’, }); const authLink = setContext((_, { headers }) => { const token = process.env.REACT_APP_TOKEN return { headers: { …headers, […]
-
Looking for an example that connects Graphql with solace
0 Is there any code example that shows how we can use the Solace pubsub+ as a source and watch for events such as insertion or update at the database at the graphql server level and leverage graphql subscription service ? I came across example with rabbitmq to achieve this but I am looking for […]
-
GqlGen incorrectly generates directives that have colon character in value field
0 I use https://github.com/99designs/gqlgen for generating golang code from graphql schema. I need to be able to add gorm tags to the resulting golang types. For that, I declare a directive for custom go tags (in schema.directives.gql): directive @goTag( key: String! value: String ) on INPUT_FIELD_DEFINITION | FIELD_DEFINITION Then I use it the following way […]