The errors in response should have the lowerCamelCase format
See original GitHub issueDescribe the bug The errors in response should have the lowerCamelCase format
To Reproduce Just have an error when execute the query, the fields inside errors are formatted as UpperCamelCase:
{
"errors": [
{
"FieldName": "hello",
"Locations": [
{
"Line": 2,
"Column": 3
}
],
"Message": "Unexpected execution error."
}
],
"data": {
"hello": null
}
}
Expected behavior Should be formatted as lowerCamelCase
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Disable check of camel case rule in eslint
Just get the same camelcase error without any change. The eslint documentation says just disable the entire rule but does not specify a...
Read more >Stuck in the camelCase assignment. I need help please
In camelCase, multi-word variable names have the first word in lowercase and the first letter of each subsequent word is capitalized. `so this ......
Read more >ModelState json serialization should be camel cased · ...
When using camelcase you probably have sent something like foo.bar in your request. I would like to suggest this change to ...
Read more >camelCase in front, snake_case in the back : r/javascript
The basic idea is that you setup api middleware to parse camelCase to snake_case on request bodies and parse snake_case to camelCase on...
Read more >What is the CamelCase naming convention?
The first letter may or may not be capitalized in CamelCase. This difference is called UpperCamelCase and lowerCamelCase. PascalCase always has the first...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We also aligned the error implementation with the 2018 spec version. So, I added the path property and also moved non-spec properties under the extension property.
0.6.0-preview-4