I post it here as well :slightly_smiling_face:
# javascripto
Ola Adolfsson
12/11/2024, 9:20 AMI post it here as well 🙂
e
Edoardo Luppi
12/11/2024, 11:57 AMHey! This is the same feedback I also gave to the K/JS team.
It is indeed a big deal for JS or TS consumers.
My first comment about it was back in June 2023.
I've opened https://youtrack.jetbrains.com/issue/KT-73827 to track it.
a
Artem Kobzar
12/11/2024, 12:38 PMHi guys. I will add this support, but I cannot say anything about deadlines.
đź‘Ť 1
e
Edoardo Luppi
12/11/2024, 12:40 PMThanks @Artem Kobzar, in my case it's not something urgent. We're are planning to increase the size of the exported SDK throughout 2025 but I still haven't come up with said plan.
o
Ola Adolfsson
12/11/2024, 1:42 PMWe're very interested in this. 🙂
đź‘€ 1
m
Márton Matusek
08/07/2025, 12:58 PMHi Guys, @Artem Kobzar,
is there any chance you will implement this in the near future? We would also like to have JSDoc for our JS api consumers.
e
Edoardo Luppi
08/07/2025, 1:01 PMConsidering that JS interop seem to be one of the priorities, I guess we'll have it sooner than later. But indeed, this missing piece is problematic, and what I do now is publish a separate readme/website for our TS consumers.
m
Márton Matusek
08/07/2025, 2:04 PMThanks @Edoardo Luppi! Do you write those docs manually?
e
Edoardo Luppi
08/07/2025, 2:05 PMYes I do. It's a little bit time consuming, but not having them would be worse.
true 1
a
Artem Kobzar
08/08/2025, 4:49 AMWe're already working on it. Some internal reworks are required, but we're already in the middle of them and plan to ship them ASAP.
The ticket to track is here: https://youtrack.jetbrains.com/issue/KT-56493/
thank you color 1
K 1
e
Edoardo Luppi
08/08/2025, 7:51 AMCurious, is the rework necessary because you don't have access to comments in the current state (while traversing the IR)?
a
Artem Kobzar
08/08/2025, 7:55 AMYes, comments are not properly saved anywhere (except metadata, and such saving is turned off by default) after FIR2IR, so we don't have this information. The same problem exists with exporting type aliases.
e
Edoardo Luppi
08/08/2025, 7:58 AMMakes sense! Does postponing the processing to the metadata layer incur in some performance penalty that you have to account for? (e.g., because now you have to traverse an additional representation)
a
Artem Kobzar
08/08/2025, 8:01 AMI don't think so, since we do the same traversing for IR to create the ExportModel representation.
Potentially, it may lead to using more memory since we need to keep both IR and FIR in the same place for a while
thank you color 1