graphql-mesh icon indicating copy to clipboard operation
graphql-mesh copied to clipboard

🕸️ GraphQL Mesh - The Graph of Everything - Federated architecture for any API service

Results 281 graphql-mesh issues
Sort by recently updated
recently updated
newest added

**Describe the bug** resolver path now must not begin with `./` **To Reproduce** Steps to reproduce the behavior: create a basic project, with config as so: ``` ... transforms: -...

stage/1-reproduction

**Describe the bug** Accessing a resource from the `mockStore` that doesn't exist doesn't handle the situation well. It complains about the `DateTime` not being defined, and not that the resource...

bug

I would like to disable Faker so that if a request is made for a property that is not being resolved, an error is thrown, or null, or something which...

**Is your feature request related to a problem? Please describe.** Yes, I tried using the Postgres handler and it doesn’t read anything from the database The AGE extension is, I...

source handler

**Describe the bug** I get the error `Expected undefined to be an input type` when an additional resolver is executed after a mutation. The same resolver works perfectly in a...

bug

Hello Urigo, I just made a presentation where I demo the use of graphql-mesh for fhir and one of the questions was the possibility of exporting the result to maybe...

feature

**Is your feature request related to a problem? Please describe.** Graphql-mesh looks like a great solution. We have many services which run on various databases, one of which is Oracle....

feature

**Is your feature request related to a problem? Please describe.** When you use mysql-input handler and some tables have "default" values, It would be desirable for those columns not to...

@santino As suggested moving this into separate issue in #2862 We have been successfully using the transform. Here are some comments: - the transform is very powerful and enables A...

If 2 requests have the same cache key. At any given point there should only be one active call to `originalResolver`. Right now the second request will also be executed...