scheduler
Advanced tools
Changelog
0.13.0 (March 10, 2015)
props
after an element is created is deprecated and will cause warnings in development mode; future versions of React will incorporate performance optimizations assuming that props aren't mutatedstatics
) are no longer autobound to the component classref
resolution order has changed slightly such that a ref to a component is available immediately after its componentDidMount
method is called; this change should be observable only if your component calls a parent component's callback within your componentDidMount
, which is an anti-pattern and should be avoided regardlesssetState
in life-cycle methods are now always batched and therefore asynchronous. Previously the first call on the first mount was synchronous.setState
and forceUpdate
on an unmounted component now warns instead of throwing. That avoids a possible race condition with Promises.this._pendingState
and this._rootNodeID
.React.findDOMNode(component)
, which should be used in place of component.getDOMNode()
. The base class for ES6-based components will not have getDOMNode
. This change will enable some more patterns moving forward.React.cloneElement(el, props)
for making copies of React elements – see the v0.13 RC2 notes for more details.ref
style, allowing a callback to be used in place of a name: <Photo ref={(c) => this._photo = c} />
allows you to reference the component with this._photo
(as opposed to ref="photo"
which gives this.refs.photo
).this.setState()
can now take a function as the first argument for transactional state updates, such as this.setState((state, props) => ({count: state.count + 1}));
– this means that you no longer need to use this._pendingState
, which is now gone.ComponentClass.type
is deprecated. Just use ComponentClass
(usually as element.type === ComponentClass
).createClass
-based components are removed or deprecated from ES6 classes (getDOMNode
, replaceState
, isMounted
, setProps
, replaceProps
).React.addons.createFragment
was added for adding keys to entire sets of children.React.addons.classSet
is now deprecated. This functionality can be replaced with several freely available modules. classnames is one such module.React.addons.cloneWithProps
can be migrated to use React.cloneElement
instead – make sure to merge style
and className
manually if desired.class
methods are no longer enumerable by default, which requires Object.defineProperty
; if you support browsers such as IE8, you can pass --target es3
to mirror the old behavior--target
option is available on the jsx command, allowing users to specify and ECMAScript version to target.
es5
is the default.es3
restores the previous default behavior. An additional transform is added here to ensure the use of reserved words as properties is safe (eg this.static
will become this['static']
for IE8 compatibility).transform
now contains sourceMap
as a JS object already, not an instance of SourceMapGenerator
.>
or }
when inside an element. Previously it would be treated as a string but now it will be treated as a parse error. The jsx_orphaned_brackets_transformer
package on npm can be used to find and fix potential issues in your JSX code.Changelog
0.12.0 (October 28, 2014)
key
and ref
moved off props object, now accessible on the element directlyReact.__internals
is removed - it was exposed for DevTools which no longer needs accessReact.createFactory
first. This is handled for you when using JSX.{...}
) introduced to deprecate this.transferPropsTo
acceptCharset
, classID
, manifest
React.renderComponent
--> React.render
React.renderComponentToString
--> React.renderToString
React.renderComponentToStaticMarkup
--> React.renderToStaticMarkup
React.isValidComponent
--> React.isValidElement
React.PropTypes.component
--> React.PropTypes.element
React.PropTypes.renderable
--> React.PropTypes.node
React.isValidClass
instance.transferPropsTo
false
from event handlers to preventDefaultReact.createFactory
key={null}
to assign implicit keysevent.getModifierState
as case sensitiveevent.charCode
list
updates correctly nowscrollLeft
, scrollTop
removed, these should not be specified as propsReact.addons.batchedUpdates
added to API for hooking into update cycleReact.addons.update
uses assign
instead of copyProperties
which does hasOwnProperty
checks. Properties on prototypes will no longer be updated correctly.@jsx React.DOM
no longer required{...}
) operator introduced to allow easier use of props