-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Use Typescript #2677
Comments
There was a discussion opened about this almost a year ago: #555 but I think Anoop said some time ago, that the migration to typescript will move to a later date because of the Golden edition. I forked Bruno in April and started rewriting it in typescript: https://github.com/its-treason/bruno. TypeScript usage is increased from 3% to 22% on my fork. |
Awesome! Is the intent for your PR to handle the entire repo or simply specific packages one at a time? |
A PR with the TS-Code might never happen. My fork started because I needed more features in Bruno and did want to wait for everything to get approved and merged. I already opened a good amount of PR with some still open: https://github.com/usebruno/bruno/pulls?q=is:pr author:its-treason |
I have checked the following:
Describe the feature you want to add
Proposing that this project migrate to use Typescript. Understand this is no small feat but feel it would improve the robustness of the code and prevent runtime errors from occurring and type-related bugs from making their way into the codebase. Perhaps a strategy in which specific packages within the app are chosen to include/migrate to Typescript and PRs are carefully reviewed by core maintainers, with the goal of converting the entire project to Typescript as a longer term goal.
I am curious if there are any reasons not to use Typescript that perhaps I am not considering. It seems like it would provide a lot of benefits to the project in terms of ruling out runtime errors due to bad type assumptions/null checks/etc at the cost an additional transpilation/build step.
Mockups or Images of the feature
N/A - Discussion/high level suggestion meant to engage the team/community about pros and cons surrounding a migration of this type.
The text was updated successfully, but these errors were encountered: