Open rhyek opened 4 years ago
I had exactly the same question in my mind.
Well, instead of asking such things, try to add something meaningful to it and push out some pull requests to make it more useful for you. I don't use typescript at all, so this is not a priority feature for me.
This was of value for @RemyJeancolas who probably just needed the capbility to parse ts files, which is totally fine seeing no problem there. This is the same addition as using coffeescript. It is not like I care about it, but there are people favoring it over the pure native javascript.
My understanding of it is: migrations are still created as javacript files, it doesn't offer any typescript definitions, and all it does is enable the cli to parse typescript itself.
So then I need to create my own ts migration file or rename a javascript one and use
any
everywhere? What is the point in that?