Is there a way to have javascript code generated w...
# javascripta
Andrew
11/15/2020, 1:44 AMIs there a way to have javascript code generated with normal function names without using @JsName? I have a large project and in most all cases I just want the javascript function name to be the same as kotlin one.
t
turansky
11/15/2020, 1:49 AMIRlegacya
Andrew
11/15/2020, 2:05 AMlegacy, although open to IR if that is better. Adding IR generates an almost empty .js file so I'd need to fix that too.
t
turansky
11/15/2020, 2:23 AMIn
IR@JsExportturansky
11/15/2020, 2:25 AMAdding IR generates an almost empty .js file so I’d need to fix that too.
@JsExportturansky
11/15/2020, 2:26 AMYou can check IR export here
a
Andrew
11/15/2020, 2:27 AMthat worked... I need to add @JsExport to every class then?
t
turansky
11/15/2020, 2:31 AMFor those, which names you want to save
turansky
11/15/2020, 2:32 AMAFAIK in
legacya
Andrew
11/15/2020, 2:41 AMlegacy should have original names? That is what im using now and got this for example. prototype.square_za3lpa$ = function (n)
Andrew
11/15/2020, 2:41 AMJust trying on a small simple project, but I have a larger one with about 100 classes so was trying to avoid needing to add annotations to everything
t
turansky
11/15/2020, 2:55 AMDo you need to save names for public classes only?
a
Andrew
11/15/2020, 3:29 AMyes
t
turansky
11/15/2020, 4:45 AMCustom compiler plugin can solve this problem too :)
a
Andrew
11/15/2020, 5:22 AMHow can I use that?
s
Svyatoslav Kuzmich [JB]
11/15/2020, 11:46 AMNames are mangled, primarily, because JS doesn’t have function overloads, which are very frequent in Kotlin.
If you need to use Kotlin code from JS, then you would want to use @JsExport explicitly, because it adds some restrictions, like prohibiting overloads, to make sure that everything looks nice from JS side.
a
Andrew
11/15/2020, 5:36 PMokay good to know, would be nice if it was non-mangled names by default then mangle overloads out of necessity. Will experiment a bit with the JsExport, it sounds like you just add that to the class then fix things it complains about, if there are any?
s
Svyatoslav Kuzmich [JB]
11/15/2020, 6:53 PM… would be nice if it was non-mangled names by default then mangle overloads out of necessity.At the first glance it would be nice, but it would make naming unstable, e.g. when you add a function overload (possibly in other module), some function that was previously non-mangled suddenly becomes mangled. In new compilation scheme we hope that JS users of Kotlin library would not be exposed to mangled names because only @JsExport-marked declarations will be visible outside.
… it sounds like you just add that to the class then fix things it complains about, if there are any?Pretty much it. This feature is currently under development, expect some bumps on the road.
4 Views