Passing Functions to Components
How do I pass an event handler (like onClick) to a component?
Pass event handlers and other functions as props to child components:
If you need to have access to the parent component in the handler, you also need to bind the function to the component instance (see below).
How do I bind a function to a component instance?
There are several ways to make sure functions have access to component attributes like this.props
and this.state
, depending on which syntax and build steps you are using.
Bind in Constructor (ES2015)
Class Properties (Stage 3 Proposal)
Bind in Render
Note:
Using
Function.prototype.bind
in render creates a new function each time the component renders, which may have performance implications (see below).
Arrow Function in Render
Note:
Using an arrow function in render creates a new function each time the component renders, which may break optimizations based on strict identity comparison.
Is it OK to use arrow functions in render methods?
Generally speaking, yes, it is OK, and it is often the easiest way to pass parameters to callback functions.
If you do have performance issues, by all means, optimize!
Why is binding necessary at all?
In JavaScript, these two code snippets are not equivalent:
Binding methods helps ensure that the second snippet works the same way as the first one.
With React, typically you only need to bind the methods you pass to other components. For example, <button onClick={this.handleClick}>
passes this.handleClick
so you want to bind it. However, it is unnecessary to bind the render
method or the lifecycle methods: we don't pass them to other components.
This post by Yehuda Katz explains what binding is, and how functions work in JavaScript, in detail.
Why is my function being called every time the component renders?
Make sure you aren't calling the function when you pass it to the component:
Instead, pass the function itself (without parens):
How do I pass a parameter to an event handler or callback?
You can use an arrow function to wrap around an event handler and pass parameters:
This is equivalent to calling .bind
:
Example: Passing params using arrow functions
Example: Passing params using data-attributes
Alternately, you can use DOM APIs to store data needed for event handlers. Consider this approach if you need to optimize a large number of elements or have a render tree that relies on React.PureComponent equality checks.
How can I prevent a function from being called too quickly or too many times in a row?
If you have an event handler such as onClick
or onScroll
and want to prevent the callback from being fired too quickly, then you can limit the rate at which callback is executed. This can be done by using:
throttling: sample changes based on a time based frequency (eg
_.throttle
)debouncing: publish changes after a period of inactivity (eg
_.debounce
)requestAnimationFrame
throttling: sample changes based onrequestAnimationFrame
(egraf-schd
)
See this visualization for a comparison of throttle
and debounce
functions.
Note:
_.debounce
,_.throttle
andraf-schd
provide acancel
method to cancel delayed callbacks. You should either call this method fromcomponentWillUnmount
or check to ensure that the component is still mounted within the delayed function.
Throttle
Throttling prevents a function from being called more than once in a given window of time. The example below throttles a "click" handler to prevent calling it more than once per second.
Debounce
Debouncing ensures that a function will not be executed until after a certain amount of time has passed since it was last called. This can be useful when you have to perform some expensive calculation in response to an event that might dispatch rapidly (eg scroll or keyboard events). The example below debounces text input with a 250ms delay.
requestAnimationFrame
throttling
requestAnimationFrame
is a way of queuing a function to be executed in the browser at the optimal time for rendering performance. A function that is queued with requestAnimationFrame
will fire in the next frame. The browser will work hard to ensure that there are 60 frames per second (60 fps). However, if the browser is unable to it will naturally limit the amount of frames in a second. For example, a device might only be able to handle 30 fps and so you will only get 30 frames in that second. Using requestAnimationFrame
for throttling is a useful technique in that it prevents you from doing more than 60 updates in a second. If you are doing 100 updates in a second this creates additional work for the browser that the user will not see anyway.
Note:
Using this technique will only capture the last published value in a frame. You can see an example of how this optimization works on
MDN
Testing your rate limiting
When testing your rate limiting code works correctly it is helpful to have the ability to fast forward time. If you are using jest
then you can use mock timers
to fast forward time. If you are using requestAnimationFrame
throttling then you may find raf-stub
to be a useful tool to control the ticking of animation frames.
Last updated