Update flow-bin to the latest version 🚀#7780
Closed
greenkeeper[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
|
A bunch of changes. We might delay a week or two to let dependencies (hopefully) catch up. Details here: https://github.com/facebook/flow/releases/tag/v0.53.0 |
Contributor
|
Yay, they made a |
Contributor
|
I added some notes to #7788 . Basically, there are some dependencies that need either ignoring or updating before |
Contributor
Author
Version 0.53.1 just got published. |
rosskevin
added a commit
to alienfast/material-ui
that referenced
this pull request
Aug 23, 2017
rosskevin
added a commit
that referenced
this pull request
Aug 23, 2017
* [flow] upgrade flow-bin * [flow] initial flow-upgrade - ran flow-upgrade - switch React.Element<any> references to React.Node - switch all react imports to `* as React` and use the React.* for access to uniformly access both function and types - linted * [flow] flow-typed install * [flow] flow-typed workaround marked libdef flow-typed/flow-typed#1165 * [flow] flow-upgrade ./test * [flow] fix flow usage of WebkitTran* * [flow] type single-only children for transitions * [flow] woohoo, resolved sticky Snackbar flow typing * [flow] more 53.1 typing * [Card] flow fixes #7854 * [flow] more flow 53.1 * [flow] fixme for #7868 * [flow] 53.1 ./examples * [flow] weak type docs for 53.1 * [flow] flow-typed workaround for flow-typed/flow-typed#1158 * [flow] workaround for flow-typed/flow-typed#1158 * [flow] require Dialog element * [flow] convert withStyles to flow * [flow] workaround brigand/babel-plugin-flow-react-proptypes#127 This isn’t a fix, it just gets past the error. I assume generated prop types are still invalid. * [flow] type TouchRipple and Ripple * [flow] type withTheme * [flow] type HOC withTheme * [flow] bind hoc BaseProps * [flow] type withWidth * [flow] type Tabs * [flow] correct requirements for HOC props * [flow] 0.53.1 conversion - tests finally run with a few errors * [flow] FormControl children were tested as optional * [Textarea] revert to target instead of currentTarget * [docs] Fix missing props in css-in-js examples (#7867) * [docs] Fix missing props in css-in-js examples `this.classes.root` wouldn't work - `this.props.classes.root' would. * Update css-in-js.md * [flow] get docs working * [Tabs] fix flow change that broke tab movement * [flow] reduce DefaultProps usage to the minimum necessary * [flow] type callback on ButtonBase * [docs] workaround react-docgen #7780 * Temporary size limit increase due to #7881
zannager
added
the
scope: system
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 0.53.0 of flow-bin just got published.
The version 0.53.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of flow-bin.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 1 commits.
25eb6b3v0.53.0See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴