graphql / graphql/graphql-spec

Question about optional terms

Open
#921 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
14.6k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

See http://spec.graphql.org/October2021/#TypeDefinition. Every type definition _may_ not declare its "important" parts: _FieldsDefinition_, _UnionMemberTypes_, _EnumValuesDefinition_, _InputFieldsDefinition_. The idea is that those parts may be declared later as extensions:
```graphql
extend type Dog {
color: String
}
```

OK. Now let's look into http://spec.graphql.org/October2021/#SchemaDefinition :
![изображение](https://user-images.githubusercontent.com/21261007/148853890-d5b700b7-7691-47e0-a88d-c78b6920364f.png)

Root operation types list is required. Why so? I think that this part should be made optional, guided by the fact that http://spec.graphql.org/October2021/#SchemaExtension may further add root operations.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.