mirror of
https://github.com/graphql-python/graphene-django.git
synced 2024-11-28 04:23:44 +03:00
add syntax highlighting
parent
3f4cfee32b
commit
41d2cb1618
|
@ -4,7 +4,7 @@ The trick here is to subclass `Connection` and declare a `connection_class` on y
|
||||||
|
|
||||||
You can now easily implement counts (or really anything) on your extended `Connection` class and use them in your queries, while retaining the built-in filtering that comes with `DjangoFilterConnectionField`:
|
You can now easily implement counts (or really anything) on your extended `Connection` class and use them in your queries, while retaining the built-in filtering that comes with `DjangoFilterConnectionField`:
|
||||||
|
|
||||||
```
|
```python
|
||||||
from graphene import ObjectType, Connection, Node, Int
|
from graphene import ObjectType, Connection, Node, Int
|
||||||
from graphene_django import DjangoObjectType
|
from graphene_django import DjangoObjectType
|
||||||
from graphene_django.filter import DjangoFilterConnectionField
|
from graphene_django.filter import DjangoFilterConnectionField
|
||||||
|
@ -57,7 +57,7 @@ This allows, on this example `schema`, querying:
|
||||||
```
|
```
|
||||||
|
|
||||||
Which returns:
|
Which returns:
|
||||||
```
|
```json
|
||||||
{
|
{
|
||||||
"data": {
|
"data": {
|
||||||
"places": {
|
"places": {
|
||||||
|
|
Loading…
Reference in New Issue
Block a user