-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Move from Flow to TypeScript #982
Comments
For me personally this is not a negative reflection on ❤️ |
I would prefer you to keep flow types up-to-date in this repo. As you can see there's not so much people who will maintain them separately. |
How about rewriting with reason? Type system is much nicer. |
@alexreardon This is an exciting development! Since Typescript is more widely used, it will also help make it easier for people to contribute to the project. Within 2019, what is your expected timeline for this migration? |
Just as we didn't want to maintain TS types when the source was in Flow, I don't think it's worth maintaining Flow types when moving to TS. @lilymatcha Alex will be back mid-Jan. See #1010 for more details. |
@treshugart Flow types will be maintained. There are existing users. |
@TrySound I am still thinking of the best way to maintain the flow types. Given they already exist I am open to having them in the repo. Once we start on the TypeScript conversion then we will have a better idea what the story could be |
Types will be quite small. So it won't take a lot of efforts to maintain them. Keeping them separately will make them out of date soon. |
@alexreardon good news for typescript. Do you guys also plan to move over Atlaskit? |
@alexreardon Great initiatives! For initial step, any thoughts of moving |
@alexreardon Has the migration to TS been abandoned? |
Hey guys, thought I would give it a shot I tried running Khan Academy's flow-to-ts on a single file and it seems to do a decent job. Sure that it's not the only change need to be done, but it seems like a good start for the bulk of the code. I'm just wondering how we should manage the existing PRs, 99% of the files would be completely different after the transition: The file names would be Would love to hear your thoughts about it Cheers UPDATE: started out here |
Here's a blog post about it. Give it a try 🙂 |
At Atlassian we consolidating on a single type system:
TypeScript
.In 2019 we plan on moving
react-beautiful-dnd
toTypeScript
.We still hope to have a good
flow
story through theflowtyped
project. We can essentially just use our existingflow
types for areact-beautiful-dnd
library definition.The text was updated successfully, but these errors were encountered: