`mutation` with duplicate fields does not throw validation error
オープン
- 主要言語
- Go
- スター
- 10.8k
- フォーク
- 1.3k
- 平均マージ
- 2日 36分
- マージ済み PR（30日）
- 26
説明
### What happened?
The following mutation:
```graphql
mutation {
evaluate(
expressions: {
date: "1"
}
)
evaluate(
expressions: {
date: "2"
}
)
}
```
Executes first mutation field only and returns:
```json
{
"data": {
"evaluate": {
"date": 1
}
}
}
```
### What did you expect?
An error similar to how `query` behaves. IE
```
Fields \"evaluate\" conflict because they have differing arguments. Use different aliases on the fields to fetch both if this was intentional.
```
The spec may have some definition of how this should be handled. Regardless, only executing one of the two mutations was unexpected.
### Versions
`v0.17.37`
コントリビューションガイド
評価
この issue はまだ評価されていません。