Skip to content
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

Update react-motion from 0.1.0 to 0.5.1 #1924

Merged
merged 2 commits into from
Sep 30, 2017
Merged

Conversation

dependencies[bot]
Copy link

@dependencies dependencies bot commented Sep 30, 2017

react-motion has been updated to 0.5.1 by dependencies.io

0.5.1

  • New flow definitions, fixes children typing

0.5.0

Breaking

  • Dropping support for older React. Currently supported versions are ^0.14.9 || ^15.3.0

Changes

  • Upgraded all React components to use ES6 classes
  • Replace React.PropTypes with prop-types package

PRs:

0.4.8

0.4.7

  • [I] didLeave for TransitionMotion! Please check the README for more.

0.4.6

No content found.

0.4.5

No content found.

0.4.4

0.4.3

0.4.2

0.4.1

  • [F] Made a mistake while publishing the bower package; fixed.

0.4.0

  • [B] spring helper's format has changed from spring(10, [120, 12]) to spring(10, {stiffness: 120, damping: 12}).
  • [B] style, styles and styles of the three respective components now only accept either a number to interpolate, or a spring configuration to interpolate. Previously, it accepted (and ignored) random key/value pairs mixed in, such as {x: spring(0), y: 'helloWorld'}. y Doesn't belong there and should be placed elsewhere, e.g. directly on the (actual react) style of the component you're assigning the interpolating values on.
  • [B] TransitionMotion got an all-around clearer API. See the upgrade guide and README section for more.
  • [B] Motion's' defaultStyle, informally accepted the format {x: spring(0)}. This is now officially unsupported. The correct format has always been {x: 0}. Setting a default style of {x: spring(whatever)} did not make sense; the configuration only applies for a style, aka destination value. Same modification applies to StaggeredMotion and TransitionMotion's defaultStyles & willEnter.
  • [B] TransitionMotion's willEnter/willLeave's signature has changed.
  • [B] The reorderKeys helper is no longer needed thanks to the changes to TransitionMotion. It's now removed.
  • [B] React-Native specific build gone. RN 0.18+ uses the vanilla Npm React package, so there's no more need for us to export a wrapper.
  • [F] Bunch of bugs gone: Storybook Contribution Guide #225, No CLI documentation that's helpful D: #212, Double Scrollbar in Full Screen Mode #179, Added typescript typings #157, Custom webpack.config linting #90, Create a static storybook builder #88.
  • [I] spring has acquired a new field as part of the new signature: precision tuning!
  • [I] Fully typed via Flow types.
  • [I] Performance improvements.

0.3.1

  • [F] Handle null and undefined in style/styles. Conflicts with NPM Shrinkwrap #181
  • [I] Library's now partially annotated with Flow.
  • [I] Related to above, the src/ folder is now exposed on npm so that you can take advantage of Flow by using: import {Motion} from 'react-motion/src/react-motion' directly, instead of the old, prebuilt import {Motion} from 'react-motion'. This is experimental and intentionally undocumented. You'll have to adjust your webpack/browserify configurations to require these original source files correctly. No harm trying of course. It's just some type annotations =).

0.3.0

0.2.7

0.2.6

  • [F] React-native warning's now gone, but also put into a separate file path. To require react-motion on react-native, do require('react-motion/native').
  • [I] Support for React 0.14.0-beta1.

0.2.5

No content found.

0.2.4

  • [I] React-native support!
  • [I] Allow returning null from children function. Fix the prepublish script #101
  • [I] defaultValue for specifying a... default value, upon mounting.
  • [I] TransitionSpring's willLeave API got simplified and now asks for an object as a return value instead of null. null is still supported, but is deprecated and will be removed in the next version. See the new docs on it here.
  • [I] Exposed a few tasteful default spring configurations under the new exported presets.

0.2.3

No content found.

0.2.2

  • [F] Import some internal modules correctly for Ubuntu/Linux node (case-sensitive for them).
  • [F] Nested springs work again.

0.2.1

No content found.

0.2.0

  • [B] willLeave returning false will now keep the key. Only null and undefined will serve as a signal to kill the disappeared key.
  • [B] willLeave previously failed to expose the second argument correspondingValueOfKeyThatJustLeft. It's now exposed correctly.
  • [F] Definitively fix the previous problem of mis-detecting React Element as object.
  • [F] willLeave is now called only once per disappearing key. It was called more than once previously as a implementation detail. Though you should never have put side-effects in willLeave. It's still discouraged now.
  • [F] If you have some this.props.handlerThatSetStateAndUnmountsSpringInOwnerRender() in Spring's endValue, Spring's already scheduled requestAnimationFrame will no longer cause an extra setState since it's unmounted. But in general, please don't put side-effect in endValue.
  • [I] Stabilize the spring algorithm. No more erratic behavior with a big amount of animated items or tab switching (which usually slows down requestAnimationFrame). Atom plugin #57
  • [I] Partial (total?) support for IE9 by using a requestAnimationFrame polyfill.

@codecov
Copy link

codecov bot commented Sep 30, 2017

Codecov Report

Merging #1924 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1924   +/-   ##
=======================================
  Coverage   21.43%   21.43%           
=======================================
  Files         261      261           
  Lines        5743     5743           
  Branches      693      682   -11     
=======================================
  Hits         1231     1231           
- Misses       3975     4009   +34     
+ Partials      537      503   -34
Impacted Files Coverage Δ
.../ui/src/modules/ui/components/left_panel/header.js 29.62% <0%> (ø) ⬆️
addons/knobs/src/components/types/Boolean.js 11.62% <0%> (ø) ⬆️
addons/info/src/components/PropTable.js 21% <0%> (ø) ⬆️
addons/knobs/src/components/types/Select.js 7.93% <0%> (ø) ⬆️
lib/ui/src/modules/shortcuts/actions/shortcuts.js 6.25% <0%> (ø) ⬆️
app/react-native/src/bin/storybook-build.js 0% <0%> (ø) ⬆️
...codemod/src/transforms/update-organisation-name.js 40.62% <0%> (ø) ⬆️
addons/info/src/components/markdown/htags.js 30% <0%> (ø) ⬆️
addons/knobs/src/components/PropForm.js 8.51% <0%> (ø) ⬆️
lib/ui/src/modules/api/configs/init_api.js 40.47% <0%> (ø) ⬆️
... and 17 more

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 8179568...2b80f41. Read the comment docs.

@Hypnosphi Hypnosphi merged commit 0772ae1 into master Sep 30, 2017
@Hypnosphi Hypnosphi deleted the react-motion-0.5.1-3.1.0 branch September 30, 2017 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants