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
As far as I understand, now the serializer for classes is generated with such an access modifier, that is, public - public, internal - internal. And there is no way to control it. If I'm wrong, please let me know.
I would like to be able to generate the internal serializer and serializer field in the companion object as well.
This can be useful for a library that internally contains public classes that can be used as parameters, but serialization is done entirely internally without additional dependencies and actions on the part of the library user.
Of course, there is an option to use public models and convert them to internal models for serialization, but this is not always possible, for example, because of the large number of objects that will give an overhead because of this.
The text was updated successfully, but these errors were encountered:
As far as I understand, now the
serializer
for classes is generated with such an access modifier, that is,public
-public
,internal
-internal
. And there is no way to control it. If I'm wrong, please let me know.I would like to be able to generate the internal serializer and
serializer
field in thecompanion object
as well.This can be useful for a library that internally contains public classes that can be used as parameters, but serialization is done entirely internally without additional dependencies and actions on the part of the library user.
Of course, there is an option to use public models and convert them to internal models for serialization, but this is not always possible, for example, because of the large number of objects that will give an overhead because of this.
The text was updated successfully, but these errors were encountered: