An option to not automatically format the data as lowerCamelCase
See original GitHub issueIs your feature request related to a problem? Please describe. Right now we are formatting the data as lowerCamelCase automatically, but we want to let the data as it is.
Describe the solution you’d like
Add an option to not automatically format the data as lowerCamelCase. This option will not effect the errors
or data
field, only with the data inside the data
field.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How to turn off or handle camelCasing in JSON response ...
Json based formatters can be configured using Microsoft.AspNetCore.Mvc.JsonOptions.JsonSerializerOptions. The default formatting is camelCase.
Read more >What is the lowerCamelCase naming convention?
Learn about lowerCamelCase, a naming convention in which a name contains multiple words joined together as a single word with a lowercase first...
Read more >Code formatting: replacing with camelCase everywhere
I have a large java project and need to reformat all field names. They are currently written like this and need to be...
Read more >How to avoid automatic data formatting in Excel
Pre-format cells as text · Select the range where you'll have your special data. It can be a column or a number of...
Read more >naming-convention.md - typescript-eslint ...
This option accepts an array of the following values, and the identifier can match any of them: camelCase - standard camelCase format -...
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
I will look into how we can do that. Maybe I will split this one and first allow this on a type basis and then introduce a global default.
Or do you mean that we automatically make the schema types case compliant?
becomes: