Open icecream17 opened 3 years ago
The tests failed, but for external reasons
Also there's this:
The tests failed, but for external reasons
Yeah, our CI seems really unhealthy 😒 . It was always a bit rickety even when this was my major focus, but it looks like entropy has made it even worse since the last time I've done work here.
Merging #2681 (8b1cfaf) into master (2053290) will not change coverage. The diff coverage is
100.00%
.
@@ Coverage Diff @@
## master #2681 +/- ##
=======================================
Coverage 93.46% 93.46%
=======================================
Files 237 237
Lines 13213 13213
Branches 1900 1900
=======================================
Hits 12349 12349
Misses 864 864
Impacted Files | Coverage Δ | |
---|---|---|
lib/atom/commands.js | 100.00% <100.00%> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 2053290...8b1cfaf. Read the comment docs.
That last commit was for the tests to run
Please be sure to read the contributor's guide to the GitHub package before submitting any pull requests.
Description of the Change
componentWillRecieveProps
is now deprecated, so this pr replaces it.https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops says: "If you need to perform a side effect (for example, data fetching or an animation) in response to a change in props, use
componentDidUpdate
lifecycle instead."componentDidUpdate
is called after updating, rather thancomponentWillRecieveProps
. If this (or some other subtle change) happens to break atom, then I'll just useUNSAFE_componentWillReceiveProps
instead.Warning text:
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
npx react-codemod rename-unsafe-lifecycles
in your project source folder.In this case, it's used for side effects (1st bullet point)
And this implies there will still be a warning when using
UNSAFE_componentWillReceiveProps
in strict-mode, so tryingcomponentDidUpdate
first.Screenshot or Gif
N/A
Applicable Issues
FixesPart ofFixes #2680