Skip to content

Releases: yahoo/react-i13n

Warning if no plugin is provided during setupI13n

19 Apr 20:57
Compare
Choose a tag to compare

Migrate to prop-types and create-react-class for React 15.5

18 Apr 18:26
Compare
Choose a tag to compare

Fix init viewport detection

17 Feb 19:15
Compare
Choose a tag to compare

#144 - with #134, it causes a regression that on page init if the parent is not in viewport, we stop all the viewport detection for the children. This release fix the issue, for a node if its parent is not in the viewport, we don't do init viewport detection for performance improvement, but we still subscribe a scrollEnd listener to handle the viewport detection.

remove coverage file from published package, follow up fix for 2.4.0

09 Feb 22:19
Compare
Choose a tag to compare

#142 - check viewportDetector before unsubscribe it, fix a js error generated by 2.4.0
#141 - Exclude code coverage from npm package thanks @roderickhsiao !

remove mixin from createI13nNode and setupI13n

09 Feb 00:14
Compare
Choose a tag to compare

#134 - This refactor is for performance improvement, we realized that a React Component performs better without mixin, with the PR, we remove mixin from createI13nNode and setupI13n, if you are still using mixin, we will encourage you to use createI13nNode instead. We will still keep I13nMixin and I13nUtil until next major bump.

We also did some performance test, as below:

link-without-react-component x 131,232 ops/sec ±1.08% (82 runs sampled)
link-wrapped-with-react-component x 111,056 ops/sec ±1.55% (88 runs sampled)
link-wrapped-with-react-component-with-i13n-mixin x 54,357 ops/sec ±1.01% (79 runs sampled)
link-wrapped-with-react-component-with-i13n-high-order-component x 64,422 ops/sec ±1.95% (84 runs sampled)

it shows a higher order component performance better than a component with a mixin, however it also shows that we have some room to improve the rendering performance to get it closer to a pure tag, we will follow up this in the near future.

filter out followLink before rendering

11 Jan 18:42
Compare
Choose a tag to compare

filter out props.followLink before rendering for removing React warning.

followLink is a hidden props to support fluxible-router/NavLink usage, with some more code cleanup we don't need this anymore. We are planning to deprecate this props entirely, so we add a warning if it's still being used.

do not override props.i13n if it's already defined

03 Nov 19:14
Compare
Choose a tag to compare

We see some case that users pass props.i13n and we are override it with createI13nNode. skip assigning props.i13n if it already exists #130

Filter out all i13n related props other than props.i13n, provide skipUtilFunctionsByProps to disable this

27 Oct 21:48
Compare
Choose a tag to compare

#125 - Filter out all i13n related props other than props.i13n when you are using setupI13n and createI13nNode. Provide skipUtilFunctionsByProps to disable this.

This helps to remove the warning from [email protected], we will still pass props.i13n for backward compatibility, if you need to prevent props.i13n to be passed to the wrapped component, please set skipUtilFunctionsByProps=true to disable this.

revert move react/react-dom to dependencies

06 Oct 20:40
Compare
Choose a tag to compare

revert the release https://github.com/yahoo/react-i13n/releases/tag/v2.2.1 , which seems breaks some app by installing a duplicated react pkg under react-i13n.

move react/react-dom to dependencies

29 Sep 19:20
Compare
Choose a tag to compare

#109 - so that app can use react-i13n without defining them in dependencies, given that react-dom might not be needed by app directly. thanks @longlho