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've had a lot of fun working kotlinpoet and I've learning a lot about annotation processing.
With regards to the builders that take class name, kclass, class, etc. Using TypeElement.asClassName() gives a deprecation warning saying to "Consider using the kotlinpoet-metadata APIs instead.". I tried to find example or search the API for how to do something like .addSuperinterface(Interface.plusParameter(TypeElement)). I can reference my Interface as KClass but it is parameterized by the TypeElement.
Is there a way to bridge the gap from TypeElement to ClassName/TypeName using kotlinpoet-metadata as is suggested in the deprecation warning?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've had a lot of fun working kotlinpoet and I've learning a lot about annotation processing.
With regards to the builders that take class name, kclass, class, etc. Using
TypeElement.asClassName()
gives a deprecation warning saying to "Consider using the kotlinpoet-metadata APIs instead.". I tried to find example or search the API for how to do something like.addSuperinterface(Interface.plusParameter(TypeElement))
. I can reference my Interface as KClass but it is parameterized by the TypeElement.Is there a way to bridge the gap from TypeElement to ClassName/TypeName using kotlinpoet-metadata as is suggested in the deprecation warning?
Beta Was this translation helpful? Give feedback.
All reactions