New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript refactoring #518
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 Keeping the issue open as direct reminder. Thanks 👍 |
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. |
@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 LiskArchive/lisk-elements#417 we'd love to hear it. |
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 Nothing will change on this front before |
Lisk Elements will be written in Typescript first - LiskArchive/lisk-elements#417 (comment). |
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. |
Hi folks,
What's actually your opinion about a Typescript refactoring? Are there any plans?
Cheers
The text was updated successfully, but these errors were encountered: