Port Glee to TypeScript about glee HOT 6 CLOSED

I am willing to contribute but am not familiar with the repo and also did not port such a large codebase to typescript before. I always started with typescript from the start.
What do you think? How we could structure the change?
How do we approach the step-by-step change?
Ts-node or typescript compilation?
Should we write tests first to ensure everything runs just fine?

from glee.

Glee misses out on a lot of benefits that typescript could provide here.

Would you mind expanding on those benefits? I'm all for porting it to TS but want to make sure we make reasonable decisions.

Should we write tests first to ensure everything runs just fine?

Since this library is still in its early days, I think it's just fine to port it and then add tests. Let's not make tests become a bottleneck.

from glee.

The main benefit of typescript is the type checking during compile time. In my eyes this can avoid many errors during runtime.
Typescript can also let us infer types from the AsyncApi document and ensure we comply with them and provide a better developer experience by autocompletion.

from glee.

I'm sold 😄 Do you want to champion this issue? I'm sure @jonaslagoni can lend a hand if needed 😄

from glee.

Should we write tests first to ensure everything runs just fine?

Yeah think this might help us now and also going forward for sure.

How do we approach the step-by-step change?

I'm happy to help here, just need some time to review the code and see how things are structured, then we can get a plan together?

from glee.

🎉 This issue has been resolved in version 0.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from glee.