We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is your use case, and why do you need this feature?
I am testing, passing objects from the SunHttp backend from Http4K all the way through Spring Controller. For example, my object:
@Serializable data class Order(val OrderName: String)
It appears in the test as {"orderName": "example"}.
After it appears in the test as Entity, I want to stringify it and deserialize it back to the Order object.
Order
Json { ignorUknownKeys = true }.deserializeFromString(EntityUtils.toString(response.entity))
I would expect it to work, or pass there a parameter that will make it work, as it is the same definition of CamelCase
Describe the solution you'd like
I would expect:
Json { ignorUknownKeys = true; polymorphicToCamelCase = true }.deserializeFromString(EntityUtils.toString(response.entity))
The text was updated successfully, but these errors were encountered:
Sorry, I don't get the idea. For changing property name, we have serial name annotation. For global policies, there's separate ticket: #33
Sorry, something went wrong.
No branches or pull requests
What is your use case, and why do you need this feature?
I am testing, passing objects from the SunHttp backend from Http4K all the way through Spring Controller.
For example, my object:
It appears in the test as {"orderName": "example"}.
After it appears in the test as Entity, I want to stringify it and deserialize it back to the
Order
object.I would expect it to work, or pass there a parameter that will make it work, as it is the same definition of CamelCase
Describe the solution you'd like
I would expect:
The text was updated successfully, but these errors were encountered: