graphene-federation
graphene-federation copied to clipboard
graphql-python
Federation implementation for Graphene.
Supported versions, v1.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 All directives are purely based on [apollo-specs](https://specs.apollo.dev/#sec-All-Schemas). Some non existent directive like`@extend` which acted like `@key` was deprecated. Migration Guide...
If we will generate SDL schema then we get: ``` """Desc 1""" type Object1 @key(fields: "field1") { """Desc field 1""" field1: DateTime """Desc field 2""" field2: ID """Desc field 3"""...
Hello graphene-federated! This PR updates examples on README, by removing unused packages and appending missing/unimported packages.
It seems Graphene Federation has stopped returning an SDL with `extend type Query`, and instead returns `type Query`. I'm not sure if this is intentional, but it is not compatible...
Fixes issue #23 > When using Enum Field as a key in containing a compound statement, validation fails and doesn't work (raises AssertionError: Invalid compound key definition for type). But...
When using Enum Field as a key in containing a compound statement, validation fails and doesn't work (raises AssertionError: Invalid compound key definition for type). But the same works if...
Hi there @erikwrede , I am using graphene-federation 0.2.0 for a GQL server using graphene 2.1.9 The query string result for SDL does not contain any **description** field meta data...
This fails: ```python @shareable @key(fields: "id") class X: pass ``` But this works: ```python @key(fields: "id") @shareable class X: pass ```
The library does not provide type hints, which results into all type information being lost when annotating types with decorators.
