Result field doesn't have Kotlin property representation. To handle it, information about corresponding Java field was added to the low-level API. So, low-level API is broken, but seemingly no one uses it. High-level API was left semantically unchanged (it still doesn't process java fields without corresponding Kotlin properties). ResultFieldUpdateHandler class was added to handle this particular use case.
Result field doesn't have Kotlin property representation. To handle it, information about corresponding Java field was added to the low-level API. So, low-level API is broken, but seemingly no one uses it. High-level API was left semantically unchanged (it still doesn't process java fields without corresponding Kotlin properties).
ResultFieldUpdateHandlerclass was added to handle this particular use case.