1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
---
title: 0.268.0 Breaking Changes
slug: breaking-changes/0.268.0
---
# v0.268.0
This release changes GlobalIDs to ID in the GraphQL schema, now instead of
having `GlobalID` as type when using `relay.Node` you'll get `ID`.
The runtime behaviour is still the same.
If you need to use the previous behaviour you can use the following config:
```python
schema = strawberry.Schema(
query=Query, config=StrawberryConfig(relay_use_legacy_global_id=True)
)
```
This release renames the generated type from `GlobalID` to `ID` in the GraphQL
schema.
This means that when using `relay.Node`, like in this example:
```python
@strawberry.type
class Fruit(relay.Node):
code: relay.NodeID[int]
name: str
```
You'd create a GraphQL type that looks like this:
```graphql
type Fruit implements Node {
id: ID!
name: String!
}
```
while previously you'd get this:
```graphql
type Fruit implements Node {
id: GlobalID!
name: String!
}
```
The runtime behaviour is still the same, so if you want to use `GlobalID` in
Python code, you can still do so, for example:
```python
@strawberry.type
class Mutation:
@strawberry.mutation
@staticmethod
async def update_fruit_weight(id: relay.GlobalID, weight: float) -> Fruit:
# while `id` is a GraphQL `ID` type, here is still an instance of `relay.GlobalID`
fruit = await id.resolve_node(info, ensure_type=Fruit)
fruit.weight = weight
return fruit
```
If you want to revert this change, and keep `GlobalID` in the schema, you can
use the following configuration:
```python
schema = strawberry.Schema(
query=Query, config=StrawberryConfig(relay_use_legacy_global_id=True)
)
```
|
