Migrate to TypeScript? #555
Replies: 8 comments 8 replies
-
|
I'm against it, I'm new here and I'm just starting to learn the code for further contribution. And TS is not about quick development and easy entry, it's about routine, where 90% of the time you describe the code. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately that's how it is and it'll always be like that. You can't really just let TS infer whatever it wants. That'd just be JavaScript with less oopsies and not really a typesafe language. |
Beta Was this translation helpful? Give feedback.
-
|
@ajaishankar @Its-treason @martinsefcik @lared What do you guys think ? If we ever decide to move core modules to TS, We should only be doing it post V1 release |
Beta Was this translation helpful? Give feedback.
-
|
Our team started to rewrite most applications in typescript, and it's been amazing so far. Getting better intellisense in the IDE and a static type checker really helped us prevent most bugs and be more productive. So I would migrate Bruno to typescript. |
Beta Was this translation helpful? Give feedback.
-
|
I'm primary Java backend developer so I'm not sure If my opinion is relevant. But I have some experience with type-safe and non type-safe programming languages and I think for smaller projects can be non type-safe languages good option but for larger one is type-safety a must. |
Beta Was this translation helpful? Give feedback.
-
|
If this is something that is on the todo list, its one of those migrations that is only going to get harder and harder to complete the longer that its put off as the application just gets more and more complex. I, like many others likely, would highly recommend bumping this higher in the queue. It will also just naturally help out with documentation and developer onboarding as it removes most of the guesswork as to how objects are structured which I find usually the biggest learning curve when taking on vanilla JS projects |
Beta Was this translation helpful? Give feedback.
-
|
@helloanoop I love typescript and would not think of starting a project without it (for all the reasons @grubersjoe mentioned) But was shocked to read recently Hotwire Turbo ditched Typescript altogether. https://world.hey.com/dhh/turbo-8-is-dropping-typescript-70165c01 In Bruno's case depends on what the collaborators feel. If it makes it difficult for them to contribute then most probably not. Personally I'm all for it, in fact the query package is already in Typescript 😄 |
Beta Was this translation helpful? Give feedback.
-
|
That said, take any popular package nowadays and chances are it will be written in Typescript. I think Turbo is an aberration... |
Beta Was this translation helpful? Give feedback.
-
|
Svelte also migrated away from Typescript to JSDoc I think. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that is actually funny - a compiler tool moving to JSDoc just because Typescript has a "build step" 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Let's do it! 😄 |
Beta Was this translation helpful? Give feedback.
-
|
TypeScript might have saved us ^^ |
Beta Was this translation helpful? Give feedback.
-
|
Maybe this one as well #717 |
Beta Was this translation helpful? Give feedback.
-
|
I'm also in the Typescript side of the force, some functions are more obscure than others, having interfaces from here and there may help us having a cleaner development in the future, especially while improving the import scripts from insomnia, postman... |
Beta Was this translation helpful? Give feedback.
-
|
I definitely agree with moving towards TypeScript in the future, especially since it seems that type annotations in JS won't be arriving anytime soon (still in stage 1). We used TS in a previous team/project & the only issue we really had was mocking with Jest. Specifically, you can't mock interfaces like in Java/C#-world, and mocking dependencies in a class was also a pain. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone! |
Beta Was this translation helpful? Give feedback.
-
Hey. Since this project has gained a lot of momentum and more and more people are contributing I think it might be sensible to start a discussion if a migration to TypeScript makes sense. It's clear that such a migration would be a huge effort and I don't know if this is something people (and the author) are interested in. Still, I think the project would benefit a lot from it:
If we want to do that, I think we would have to do it in small steps. Maybe start with
allowJs: trueand migrate package for package. You can also infer TypeScript types based on the Yup schema. If you knew the exact data structure of aCollectionetc. everywhere that alone would be a huge improvement regarding maintainability in my opinion.Beta Was this translation helpful? Give feedback.
All reactions