Collection types in generated d.ts file

JavaScript
1

In my code, I export a function like this:

@JsExport
fun calculatePrice(
  position: FuturePosition,
  positionList: List<FuturePosition>,
  balanceList: List<FutureBalance>,
  bracketList: List<FutureBracket>,
): Double {

Although I got the following warning:
Exported declaration uses non-exportable parameter type: List<FuturePosition>

截屏2021-12-29 下午10.33.40
截屏2021-12-29 下午10.33.401450×342 48.9 KB

I’ve found that if I export List and ArrayList to Javascript, I can use them to create arguments for calculatePrice function. Here is my way to export List and ArrayList.

@JsExport
fun <E> KotlinArrayList(vararg elements: E): ArrayList<E> = arrayListOf(*elements)

@JsExport
fun <E> KotlinList(vararg elements: E): List<E> = listOf(*elements)

But in generated d.ts file, it seems we can’t find kotlin namespace, so their types are all any.

截屏2021-12-29 下午10.27.56
截屏2021-12-29 下午10.27.561542×446 86.7 KB

Is there any way I can get right type for collections or easier way to export List and ArrayList?

2

On exportable code in Kotlin/JS, I always use Array instead of List, they are natively supported in JS. Not ideal, I know, especially if you have to deal with those on the Kotlin side a lot, but it makes interoperability much better.

3

Another question, are you adding @JsExport on your other Future* classes? Those needed to be exported as well, as they are part of the public API of your exported function.

4

Yes, We also decide to use Array instead of List.
But in the future, we may use Map in our code. At that time this problem will occur again.
Is there any suggestions to integrate Map data?

And yes these Future* classes are all exported by @JsExport.

5

No, I have no suggestions for the Map issue. Maps in Java/Kotlin are very different from Objects in JS, so there is no 1:1 correlation.