Hi folks,
What's actually your opinion about a Typescript refactoring? Are there any plans?
Cheers
ppetzold
All 7 comments
Hi @ppetzold,
No concrete plans but definitely something we want to tackle. Until now, there were other priorities.
We will schedule for inclusion after 1.0.0 is out of the way I think.
Keeping the issue open as direct reminder. Thanks 馃憤
karmacoma
on 28 Mar 2017
Looking forward to this as it will help catching bugs, doing maintenance and enabling code completion/IntelliSense for those building dApps in the future.
Huge effort, though.
kazzkiq
on 22 Nov 2017
@ppetzold @ZandorZ @kazzkiq We'll be implementing a type system in lisk-js first and use the experience to inform our decisions in other projects. If you have anything helpful to add to https://github.com/LiskHQ/lisk-js/issues/417 we'd love to hear it.
willclarktech
on 22 Nov 2017
Any updates on the thoughts on Typescript refactoring since we're there now?
Also it sucks that refactoring gets harder and hader as more code gets written in JS. 馃槩
goktugyil
on 19 Jan 2018
@goktugyil Nothing will change on this front before 1.0.0 is released.
willclarktech
on 22 Jan 2018
Lisk Elements will be written in Typescript first - https://github.com/LiskHQ/lisk-elements/issues/417#issuecomment-420635666.
MaciejBaj
on 14 Sep 2018
Moving to TypeScript is on Lisk Core Roadmap (https://lisk.io/roadmap). I am closing the issue, it will be re-opened in a milestone form when after all of the scheduled to move modules will already be extracted from Lisk Core to Lisk Elements.
MaciejBaj
on 27 Nov 2018
Related issues
karmacoma
路
3Comments
willclarktech
路
4Comments
slaweet
路
3Comments
hendrikhofstadt
路
4Comments
Isabello
路
4Comments
Most helpful comment
Hi @ppetzold,
No concrete plans but definitely something we want to tackle. Until now, there were other priorities.
We will schedule for inclusion after
1.0.0is out of the way I think.Keeping the issue open as direct reminder. Thanks 馃憤