-
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
Remove flow #2028
Remove flow #2028
Conversation
💥 No ChangesetLatest commit: df40e7c Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂 If these changes should be published to npm, you need to add a changeset. Click here to learn what changesets are, and how to add one. Click here if you're a maintainer who wants to add a changeset to this PR |
can we create a branch/tag which has Flow (just before this merge)? it would be helpful to use them when we go for TypeScript (soon hopefully). lot of typings can be copied to TypeScript as is even in jsdoc format. see #1373 |
We don't really need to make a branch since we can look at the git history to get to a version of the repo with flow in it |
A git tag would be helpful and easy to get to |
Just pushed a |
We've discussed it and we're going to remove Flow. Maintaining our usage of Flow has been causing more pain than the benefit we get out of it.