You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using generateKotlinNullableClasses, it becomes impossible to use toString in the debugger to view the full scope of all the fields that were actually accessed.
It would be nice if the generated functions held information whether or not the field were present or not, that way, a sane toString could be generated that checks if each field were present before adding it to the printed string.
The text was updated successfully, but these errors were encountered:
When using
generateKotlinNullableClasses
, it becomes impossible to usetoString
in the debugger to view the full scope of all the fields that were actually accessed.It would be nice if the generated functions held information whether or not the field were present or not, that way, a sane
toString
could be generated that checks if each field were present before adding it to the printed string.The text was updated successfully, but these errors were encountered: