Azure / Azure/data-api-builder

[Bug]: Incorrect parsing of default values when GQL context variables are used

Open
#2,079 6 comments 0 reactions 1 assignee Claimed by @ayush3797 View on GitHub
bug graphql
Dominant language
C#
Stars
1.5k
Forks
370
Avg merge
3d 17h
Merged PRs (30d)
8

Description

Consider the table definition for `type_table`:

image

The column `float_types` is a column which has a default value of `1.1`. Now, if we execute a GQL create mutation on this table and:

1. Provide input using GQL context variables
2. Omit value for the `float_types` column (since it has a default value so we don't need to specify it)

We get an error:

```json
{
"errors": [
{
"message": "Float cannot parse the given literal of type `StringValueNode`.",
"path": [
"item",
"float_types"
],
"extensions": {
"field": "CreateSupportedTypeInput.float_types",
"fieldType": "Float"
}
}
]
}
```

image

Similar behavior was observed when `int_types` was given a default value.

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.