hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 01:12:56 +03:00
Code Issues Projects Releases Wiki Activity

docs: add ref docs for --null-in-nonnullable-variables server option

Browse Source 
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10533
GitOrigin-RevId: 5ffcec9f5549515a749a89db818542da2950b5a2
This commit is contained in:
Rakesh Emmadi 2023-12-05 17:29:50 +05:30 committed by hasura-bot
parent 1578f29239
commit be184101a4
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docs/docs/deployment/graphql-engine-flags/reference.mdx
View File

@ -704,6 +704,37 @@ Multiplexed live queries are split into
| **Default** | `100` |
| **Supported in** | CE, Enterprise Edition, Cloud |
### Null in Non-nullable Variables
GraphQL query validation is fixed in [`v2.36.0-beta.1`](https://hasura.io/changelog/community-edition/v2.36.0-beta.1),
where queries that assigned a `null` value to variables with non-nullable type were allowed.
Example:
```graphql
query ($user_id: Int!) {
users(where: {id: {_eq: $user_id}}){
id name
}
}
```
variables
```json
{
"user_id": null
}
```
To rollback to the old behavior, i.e., allow `null` value for non-nullable variables, use this option.
| | |
|---------------------|-----------------------------------------------------------------|
| **Flag** | `--null-in-nonnullable-variables <true-or-false>` |
| **Env var** | `HASURA_GRAPHQL_BACKWARDS_COMPAT_NULL_IN_NONNULLABLE_VARIABLES` |
| **Accepted values** | Boolean |
| **Options** | `true` or `false` |
| **Default** | `false` |
| **Supported in** | CE, Enterprise Edition, Cloud - from `v2.36.0-beta.1` |
### Number of Retries
:::warning Notice