graphql-python / graphql-python/graphql-relay-py
Why are nodes optional?
- Langage dominant
- Python
- Étoiles
- 144
- Forks
- 41
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
I was trying to dig through this to figure it out, and I apologize if there's a good reason for this.
It seems to me that a paginated connection (e.g. `DjangoConnectionField` or `DjangoFilterConnectionField`) always has edges and nodes. What's the use case for these being nullable?
The reason I bring this up is because, when using TypeScript with the generated schema, it results in lengthy checks like this:
```tsx
{edges.map(edge => (
{edge &&
edge.node &&
edge.node.id (
...
```
As far as I can tell this is set up here:
https://github.com/graphql-python/graphql-relay-py/blob/master/graphql_relay/connection/connection.py#L44
Could there be `required` on edges/nodes? At least as an option it'd be a breaking change. Right now I'm not sure how to override this.
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.