ariadne-graphql-modules
ariadne-graphql-modules copied to clipboard
mirumee
Ariadne package for implementing Ariadne GraphQL schemas using modular approach.
Subscription type acts like regular object type, except for its fields one has to set both `resolver` and `source` functions.
It is possible that code implemented using new API will fail to validate with MyPy because of its magicalness. If this is the case, we will have to explore implementing...
This PR adds `next` package to `ariadne_graphql_modules` containing future API that supports both schema first and code first approaches to development # TODO - [x] Fix build (rename `type` to...
Instead of a single markdown file like we've did for Ariadne GraphQL Proxy, we could create a directory named `docs` in repo, create `index.md` file with table of contents and...
We need to provide people using previous version of library with a way to move to new version without having to rewrite whole GraphQL API in single commit or change....
While mutations are already possible in future API via `MutationType(ObjectType)` sublclassing, we could also have extra `MutationType` base class that would represent single field on `mutation`: ```python class ErrorType(GraphQLObject): path:...
We need to make a decision if we want to have custom `DirectiveType` or try being clever about directive class from `ariadne` package.
I have a fairly large GraphQL API written in `graphene`. I am interested in moving to `ariadne`, but I'd rather not migrate the whole thing in one go. So, since...
We should support code-first approach to type definition in addition to current schema-first one. My original idea was to do this through decorator (like how Strawberry does it) but my...
Hello, thank you for this package, I really like this modular approach. I was wondering if anyone has any pointers on how to combine `ariadne_graphql_modules.make_executable_schema` with [`ariadne.contrib.federation.make_federated_schema`](https://ariadnegraphql.org/docs/apollo-federation). Thank you!
