Question for folks using the new JS IR: Does `@JsE...

# javascript

[ankushg]

Question for folks using the new JS IR: Does @JsExport also prevent name mangling? Or do you need to use both @JsExport and @JsName for that?

[turansky]

Yes, it does

[ankushg]

Nice!

It seems like @JsExport is responsible for a few different things, but the actual behavior varies depending on the compiler:
• exporting TS types (new IR only)
• preventing DCE from removing (new IR only?)
• preventing name mangling (new IR and legacy)
Is this accurate?

[turansky]

All 3 things works in IR only

[turansky]

Names are non-mangled in legacy by default, but it’s not a contract 🙂

[turansky]

Non-mangled names - contract of export feature

[adk]

There is a gotcha, where a non-JsExport'ed implementation of a JsExport'ed interface is unusable, because the members of the impl class are all prefixed with underscore. No amount of JsName will help with this.

[turansky]

Looks like external interfaces can solve this problem

[adk]

Not sure what you mean by that? Do you have a link to some docs I could look at?

[adk]

do you mean the external declarations used on the kotlin side when you wan to call JS code?

[turansky]

If JsName doesn't work for mangling block, than you can create external interface and implement it

[turansky]

External interface properties/methods will be non-mangled

[adk]

Yes, but this doesn't work unless the class that implements the interface is also JsExported

[adk]

because the member names of the class are prefixed with underscore, while those of the interface are not

[adk]

if you JsExport a class, it does not have this problem, but an interface does

[turansky]

Is there example?

[adk]

Let me spend a little time to put something together - the code I currently have is closed.