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
I think allowing generics would be more difficult than you suggest, but the main reason I haven't put any effort into it is that there is a simple workaround.
If you create a typealias as follows:
typealias MapStringAny = Map<String, Any>
then you can use MapStringAny in your classMappings setting. It may not be ideal, but it gets around the problem with relatively little effort.
Uh oh!
There was an error while loading. Please reload this page.
If a class mapping is performed with generics, for example
Then the resulting import in the generated code looks like:
I think it might be an easy fix to change the following function in
Target
from:to:
Alternatively, this could be changed to be stripped off when processing the
className
within the variousCustomClass
sublcass constructors.The text was updated successfully, but these errors were encountered: