-
Notifications
You must be signed in to change notification settings - Fork 10
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
add flow-coverage script, add aphrodite flow types #249
Conversation
Deploy preview for wonder-blocks ready! Built with commit 8065a63 |
Codecov Report
@@ Coverage Diff @@
## master #249 +/- ##
==========================================
- Coverage 85.91% 85.17% -0.74%
==========================================
Files 103 103
Lines 1363 1376 +13
Branches 277 277
==========================================
+ Hits 1171 1172 +1
- Misses 163 175 +12
Partials 29 29
Continue to review full report at Codecov.
|
…x resulting flow errors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome - really glad our coverage is improving and we have a way of tracking it! Once we have LCOV support that'll be ideal. One or two potential small issues, would be good to fix before landing.
@@ -15,9 +15,6 @@ const styles = StyleSheet.create({ | |||
row: { | |||
flexDirection: "row", | |||
}, | |||
strutLike: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay for dead code removal!
/** | ||
* This is a labeled 🔘 or ☑️ item. This is an internal component that's wrapped | ||
* by ChoiceField or Choice. Choice should be used in a CheckboxGroup or in a | ||
* RadioGroup. ChoiceField is the variant used outside of such a group. The two | ||
* are different to allow for more explicit flow typing. Choice has many of its | ||
* props auto-populated, but ChoiceField does not. | ||
*/ | ||
export default class ChoiceInternal extends React.Component<Props> { | ||
*/ export default class ChoiceInternal extends React.Component<Props> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the weird spacing issue that @wishdasher was seeing with Prettier, would be good to fix this! Maybe we need to upgrade Prettier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updating prettier does not resolve this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like this would be pretty easy to fix, just add a rule that states code should not appear on a line after a block comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to leave this as is otherwise we'll end up with this change the next time someone edits this file.
package.json
Outdated
@@ -29,6 +30,10 @@ | |||
"author": "", | |||
"license": "MIT", | |||
"devDependencies": { | |||
"//": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛑 Hmm - this got moved. Maybe you could move it out of devDependencies
and update to specifically reference enzyme-adapter-react-16
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for noticing this. I guess I'll avoid running yarn add
in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess if we follow the same pattern as the package.json in webapp this shouldn't be an issue.
😭 |
Adding aphrodite.flow.js bumped our flow coverage from 85% to 91%. This was computed using the
flow-coverage-report
npm package. It doesn't support lcov yet so we can't upload the reports to codecov. See rpl/flow-coverage-report#67. In the meantime you can run it manually withyarn run flow-coverage
.TODO:
flowtype/no-types-missing-file-annotation
eslint rule// @flow
to files missing itflow
errors.