Just throwing it out there ahead of time... Would ...
# javascript
e
Just throwing it out there ahead of time... Would be cool if we could see
EagerInitialization
un-deprecated for 2.5.0 👀
âž• 1
p
Is there any plans?
a
I'm preparing a PR (let's cross fingers that the library team will accept with LGTM 😅)
🤞 1
gratitude thank you 1
e
Oh nice. Should an alias be in place? E.g., keeping
EagerInitialization
deprecated as an alias, but exporting
JsEagerInitialization
? Or is the current name good enough?
a
I believe if we can do this for JS, for the other backends it would be also a question if they should un-deprecate it
e
Makes sense! So basically the idea is to keep the annotation name target-agnostic.
a
Folks, could I ask you to describe your use-cases here: youtrack.jetbrains.com/issue/KT-63218?
✅ 2
e
I've added a use case that is currently not supported, just to give it more scope for the future.