ChatGPT解决这个技术问题 Extra ChatGPT

React js onClick can't pass value to method

I want to read the onClick event value properties. But when I click on it, I see something like this on the console:

SyntheticMouseEvent {dispatchConfig: Object, dispatchMarker: ".1.1.0.2.0.0:1", nativeEvent: MouseEvent, type: "click", target

My code is working correctly. When I run I can see {column} but can't get it in the onClick event.

My Code:

var HeaderRows = React.createClass({
  handleSort:  function(value) {
    console.log(value);
  },
  render: function () {
    var that = this;
    return(
      <tr>
        {this.props.defaultColumns.map(function (column) {
          return (
            <th value={column} onClick={that.handleSort} >{column}</th>
          );
        })}
        {this.props.externalColumns.map(function (column) {
          // Multi dimension array - 0 is column name
          var externalColumnName = column[0];
          return ( <th>{externalColumnName}</th>);
        })}
      </tr>
    );
  }
});

How can I pass a value to the onClick event in React js?

possible duplicate of OnClick Event binding in React.js
consider using self instead of that. That is fairly misleading as it should be synonymous with "this" (not important really though, to each his own)
Using bind method and arrow method we can pass the value to Onclick event
Agreed with @WiredPrairie and the guy named ZenMaster explained precisely and effectively.
What you are doing wrong there is passing the return value of the call to handleSort and of course, it happens at page load

t
theSereneRebel

Easy Way

Use an arrow function:

return (
  <th value={column} onClick={() => this.handleSort(column)}>{column}</th>
);

This will create a new function that calls handleSort with the right params.

Better Way

Extract it into a sub-component. The problem with using an arrow function in the render call is it will create a new function every time, which ends up causing unneeded re-renders.

If you create a sub-component, you can pass handler and use props as the arguments, which will then re-render only when the props change (because the handler reference now never changes):

Sub-component

class TableHeader extends Component {
  handleClick = () => {
    this.props.onHeaderClick(this.props.value);
  }

  render() {
    return (
      <th onClick={this.handleClick}>
        {this.props.column}
      </th>
    );
  }
}

Main component

{this.props.defaultColumns.map((column) => (
  <TableHeader
    value={column}
    onHeaderClick={this.handleSort}
  />
))}

Old Easy Way (ES5)

Use .bind to pass the parameter you want, this way you are binding the function with the Component context :

return (
  <th value={column} onClick={this.handleSort.bind(this, column)}>{column}</th>
);

react gives warning when i use like your code. I change my code to onClick={that.onClick.bind(null,column)}
How would you use this with a <a> tag where you need to pass the event, in order to use preventDefault()
@SimonH The event will be passed as the last argument, after the arguments you pass via bind.
Is this not bad for performance? wont a new function be created on each render?
@AndrewMcLagan It is. I found this to describe the rule and the most performant solution.
S
Sagiv b.g

There are nice answers here, and i agree with @Austin Greco (the second option with separate components)
There is another way i like, currying.
What you can do is create a function that accept a parameter (your parameter) and returns another function that accepts another parameter (the click event in this case). then you are free to do with it what ever you want.

ES5:

handleChange(param) { // param is the argument you passed to the function
    return function (e) { // e is the event object that returned

    };
}

ES6:

handleChange = param => e => {
    // param is the argument you passed to the function
    // e is the event object that returned
};

And you will use it this way:

<input 
    type="text" 
    onChange={this.handleChange(someParam)} 
/>

Here is a full example of such usage:

const someArr = ["A", "B", "C", "D"]; class App extends React.Component { state = { valueA: "", valueB: "some initial value", valueC: "", valueD: "blah blah" }; handleChange = param => e => { const nextValue = e.target.value; this.setState({ ["value" + param]: nextValue }); }; render() { return (

{someArr.map(obj => { return (


); })}
); } } const rootElement = document.getElementById("root"); ReactDOM.render(, rootElement);

Note that this approach doesn't solve the creation of a new instance on each render. I like this approach over the other inline handlers as this one is more concise and readable in my opinion.

Edit: As suggested in the comments below, you can cache / memoize the result of the function.

Here is a naive implementation:

let memo = {}; const someArr = ["A", "B", "C", "D"]; class App extends React.Component { state = { valueA: "", valueB: "some initial value", valueC: "", valueD: "blah blah" }; handleChange = param => { const handler = e => { const nextValue = e.target.value; this.setState({ ["value" + param]: nextValue }); } if (!memo[param]) { memo[param] = e => handler(e) } return memo[param] }; render() { return (

{someArr.map(obj => { return (


); })}
); } } const rootElement = document.getElementById("root"); ReactDOM.render(, rootElement);


This should be the accepted answer. REALLY easy to implement and you don't need to create any other components or bind differently. Thank you!
Looks better, but from a performance perspective though, currying doesn't really help, because if you call handleChange twice, with the same param, you get two functions that the JS engine consider to be separate objects, even if they do the same thing. So you still get a re-render. For the sake of performance, you would need to cache the results of handleChange to get the performance advantage. Like handleChange = param => cache[param] || (e => { // the function body })
This is the perfect answer if you fulfill the advice from @travellingprog
Can anyone provide a link or explain how this caching mechanism works ? thanks.
If you use currying, new function will be created at each render. Same performance problem occurs as passing an arrow function.
a
aikeru

Nowadays, with ES6, I feel we could use an updated answer.

return (
  <th value={column} onClick={()=>this.handleSort(column)} >{column}</th>
);

Basically, (for any that don't know) since onClick is expecting a function passed to it, bind works because it creates a copy of a function. Instead we can pass an arrow function expression that simply invokes the function we want, and preserves this. You should never need to bind the render method in React, but if for some reason you're losing this in one of your component methods:

constructor(props) {
  super(props);
  this.myMethod = this.myMethod.bind(this);
}

You never need to bind render() because it is called by React. If anything, you need to bind the event handlers, and only when you are not using arrows.
Note it’s also best to pass props to super() or this.props will be undefined during constructor which can get confusing.
To achieve what? You can define a handler inside functional component and pass it. It will be a different function every render so if you have determined with a profiler that it gives you perf issues (and only if you’re actually sure in this!), consider using a class instead.
Thanks Aikeru. Ah ok so you are saying if you declare the foo method as an arrow function on the class itself, then reference it using the this context then its only created once instead of declaring it inside the onClick where its creating the same function every time you click the button. Is that correct in my thinking.
@zuckerburg onClick={() => alert('hi')} will not immediately alert, nor will onClick={this.showAlert} because in both cases you are passing (not invoking) a function.
B
Brandon

[[h/t to @E.Sundin for linking this in a comment]

The top answer (anonymous functions or binding) will work, but it's not the most performant, as it creates a copy of the event handler for every instance generated by the map() function.

This is an explanation of the optimal way to do it from the ESLint-plugin-react:

Lists of Items A common use case of bind in render is when rendering a list, to have a separate callback per list item:

const List = props => (
      <ul>
        {props.items.map(item =>
          <li key={item.id} onClick={() => console.log(item.id)}>
            ...
          </li>
        )}
      </ul>
    );

Rather than doing it this way, pull the repeated section into its own component:

const List = props => (
      <ul>
        {props.items.map(item =>
          <ListItem 
            key={item.id} 
            item={item} 
            onItemClick={props.onItemClick} // assume this is passed down to List
           />
        )}
      </ul>
    );


const ListItem = props => {
  const _onClick = () => {
    console.log(props.item.id);
  }
    return (
      <li onClick={_onClick}>
        ...
      </li>
    );

});

This will speed up rendering, as it avoids the need to create new functions (through bind calls) on every render.


Does react invoke those functions with call/apply, then, under the hood, and avoid using bind internally?
Is there a way to doing this using a stateless component?
@CarlosMartinez good eye, i updated the example--they should've been stateless functional components (SFC) in the first place. Generally, if a component doesn't ever use this.state, you can safely swap it out with an SFC.
Hmm, I don't get how this is more performant? Won't the ListItem function be invoked every time, and thus the _onClick function will be created every render.
I'm far from an expert here, but as I understand it, in the 'correct' pattern, there's only one instance of the handler and it's passed the prop for whichever instance of the component calls it. In the bind example (ie, the 'wrong' pattern), there's one instance of the handler for every instantiated component. It's sort of the memory equivalent of writing the same function thirty times vice writing it once & calling it where needed.
S
Santiago Ramirez

This is my approach, not sure how bad it is, please comment

In the clickable element

return (
    <th value={column} onClick={that.handleSort} data-column={column}>   {column}</th>
);

and then

handleSort(e){
    this.sortOn(e.currentTarget.getAttribute('data-column'));
}

This is an approach I was thinking of, it feels a little hacky but avoids creating a new component. I am not sure if getAttribute is better or worse perf-wise compared to pulling into a separate component.
I think it's a good solution because it is very simple. But it works only with string values, if you want an object it doesn't work.
For an object you would need to do encodeURIComponent(JSON.stringify(myObj)), then to parse it, JSON.parse(decodeURIComponent(myObj)). For functions I'm pretty sure this wont work without eval or new Function(), both of which should be avoided. For these reasons I don't use data-attributes to pass data in React/JS.
I want to add I don't use this often and only for minor things. But usually I just create a component and pass the data as props to it. Then either handle the click inside that new component or pass a onClick function to the component. Like is explained in Brandon answer
dataset can be accessed directly on this way on modern browsers (including IE11): e.currentTarget.dataset.column
r
ravibagul91

this example might be little different from yours. but i can assure you that this is the best solution you can have for this problem. i have searched for days for a solution which has no performance issue. and finally came up with this one.

class HtmlComponent extends React.Component {
  constructor() {
    super();
    this.state={
       name:'MrRehman',
    };
    this.handleClick= this.handleClick.bind(this);
  }

  handleClick(event) {
    const { param } = e.target.dataset;
    console.log(param);
    //do what you want to do with the parameter
  }

  render() {
    return (
      <div>
        <h3 data-param="value what you wanted to pass" onClick={this.handleClick}>
          {this.state.name}
        </h3>
      </div>
    );
  }
}

UPDATE

incase you want to deal with objects that are supposed to be the parameters. you can use JSON.stringify(object) to convert to it to string and add to the data set.

return (
   <div>
     <h3 data-param={JSON.stringify({name:'me'})} onClick={this.handleClick}>
        {this.state.name}
     </h3>
   </div>
);

this does not work when the data passed is an object
use JSON.stringify to fix the issue. @SlimSim . that should do the trick
If you need to use JSON.stringify for this problem then its probably not the correct method. The process of stringification takes a lot of memory.
in most of the cases you would only pass ID as params, and get the object details based on that ID from your source object. and why and how does it take a lot of memory, i know JSON stringify is slow, but the click Fn is async and it will have no or 0 effect on dom, once constructed
T
Tom Bombadil

React Hooks Solution 2022

const arr = [
  { id: 1, txt: 'One' },
  { id: 2, txt: 'Two' },
  { id: 3, txt: 'Three' },
]

const App = () => {
  const handleClick = useCallback(
    (id) => () => {
      console.log("ID: ", id)
    },
    [],
  )

  return (
    <div>
      {arr.map((item) => (
        <button onClick={handleClick(item.id)}>{item.txt}</button>
      ))}
    </div>
  )
}

You can pass a function to useCallback's return, you can then call your function normally in the render by passing params to it. Works like a charm! Just make sure you set your useCallback's dependency array appropriately.

Best Solution with React >= 16

The cleanest way I've found to call functions with multiple parameters in onClick, onChange etc. without using inline functions is to use the custom data attribute available in React 16 and above versions.

const App = () => {
  const onClick = (e) => {
    const value1 = e.currentTarget.getAttribute("data-value1")
    const value2 = e.currentTarget.getAttribute("data-value2")
    const value2 = e.currentTarget.getAttribute("data-value2")
    console.log("Values1", value1)
    console.log("Values2", value2)
    console.log("Values3", value3)
  }
  return (
    <button onClick={onClick} data-value1="a" data-value2="b" data-value3="c" />
  )
}

Above example is for a functional component but the implementation is pretty similar even in class components.

This approach doesn't yield unnecessary re-renders because you aren't using inline functions, and you avoid the hassle of binding with this.

It allows you to pass as many values as you would like to use in your function.

If you are passing values as props to your children to be used in the Child Component's onClick, you can use this approach there as well, without creating a wrapper function.

Works with array of objects as well, in cases where you want to pass the id from the object to the onClick, as shown below.

const App = () => {
  const [arrState, setArrState] = useState(arr)

  const deleteContent = (e) => {
    const id = e.currentTarget.getAttribute("data-id")
    const tempArr = [...arrState]
    const filteredArr = tempArr.filter((item) => item.id !== id)
    setArrState(filteredArr)
  }

  return (
    <div>
      {arrState.map((item) => (
        <React.Fragment key={item.id}>
          <p>{item.content}</p>
          <button onClick={deleteContent} data-id={item.id}>
            Delete
          </button>
        </React.Fragment>
      ))}
    </div>
  )
}

I love this data- comment. So clean and simple
Actually the use of useEffect in your example won't help, as the callback returned by useCallback is still going to create new functions on every render.
@MarcesEngel Depends on what you pass to the useCallback's array.
@TomBombadil would you elaborate? Only the creation of the outer function is memoized, not its results. This means the returned function will create a new function on each execution, in this case each render of the containing component. Is there any fault in this train of thought?
@MarcesEngel Yeah you are probably right. But where I work, the projects have strict ES Lint rules, so no inline functions. The first one surely works to appease ES Lint. Also, I did not really mention anything about performance improvements really. Just that this is also one way. I usually go with the second one. A little bit more work but in most cases works. You can toString an entire object and pass it in for the second. Stupid perhaps, but React.FC doesn't really give us a lot in respect to passing params to functions in JSX.
C
Charith Jayasanka

Simply create a function like this

  function methodName(params) {
    //the thing  you wanna do
  }

and call it in the place you need

 <Icon onClick = {() => { methodName(theParamsYouwantToPass);} }/>

Oc 😶😶😶😶😶😶
hahaha, it's crazy that this is working! You don't even need the curly braces and parenthesis. Anyone knows how React handles the anonymous function here?
V
Vladimirs Matusevics
class extends React.Component {
    onClickDiv = (column) => {
        // do stuff
    }
    render() {
        return <div onClick={() => this.onClickDiv('123')} />
    }
}

The same - new DOM on each render. So React will update DOM each time.
j
jhchnc

I realize this is pretty late to the party, but I think a much simpler solution could satisfy many use cases:

    handleEdit(event) {
        let value = event.target.value;
    }

    ...

    <button
        value={post.id}
        onClick={this.handleEdit} >Edit</button>

I presume you could also use a data- attribute.

Simple, semantic.


P
Po Rith

Making alternate attempt to answer OP's question including e.preventDefault() calls:

Rendered link (ES6)

<a href="#link" onClick={(e) => this.handleSort(e, 'myParam')}>

Component Function

handleSort = (e, param) => {
  e.preventDefault();
  console.log('Sorting by: ' + param)
}

B
Brett DeWoody

One more option not involving .bind or ES6 is to use a child component with a handler to call the parent handler with the necessary props. Here's an example (and a link to working example is below):

var HeaderRows = React.createClass({
  handleSort:  function(value) {
     console.log(value);
  },
  render: function () {
      var that = this;
      return(
          <tr>
              {this.props.defaultColumns.map(function (column) {
                  return (
                      <TableHeader value={column} onClick={that.handleSort} >
                        {column}
                      </TableHeader>
                  );
              })}
              {this.props.externalColumns.map(function (column) {
                  // Multi dimension array - 0 is column name
                  var externalColumnName = column[0];
                  return ( <th>{externalColumnName}</th>
                  );
              })}
          </tr>);
      )
  }
});

// A child component to pass the props back to the parent handler
var TableHeader = React.createClass({
  propTypes: {
    value: React.PropTypes.string,
    onClick: React.PropTypes.func
  },
  render: function () {
    return (
      <th value={this.props.value} onClick={this._handleClick}
        {this.props.children}
      </th>
    )        
  },
  _handleClick: function () {
    if (this.props.onClick) {
      this.props.onClick(this.props.value);
    }
  }
});

The basic idea is for the parent component to pass the onClick function to a child component. The child component calls the onClick function and can access any props passed to it (and the event), allowing you to use any event value or other props within the parent's onClick function.

Here's a CodePen demo showing this method in action.


P
Pramesh Bajracharya

You can simply do it if you are using ES6.

export default class Container extends Component {
  state = {
    data: [
        // ...
    ]
  }

  handleItemChange = (e, data) => {
      // here the data is available 
      // ....
  }
  render () {
     return (
        <div>
        {
           this.state.data.map((item, index) => (
              <div key={index}>
                  <Input onChange={(event) => this.handItemChange(event, 
                         item)} value={item.value}/>
              </div>
           ))
        }
        </div>
     );
   }
 }

n
nandu

Implementing show total count from an object by passing count as a parameter from main to sub components as described below.

Here is MainComponent.js

import React, { Component } from "react";

import SubComp from "./subcomponent";

class App extends Component {

  getTotalCount = (count) => {
    this.setState({
      total: this.state.total + count
    })
  };

  state = {
    total: 0
  };

  render() {
    const someData = [
      { name: "one", count: 200 },
      { name: "two", count: 100 },
      { name: "three", count: 50 }
    ];
    return (
      <div className="App">
        {someData.map((nameAndCount, i) => {
          return (
            <SubComp
              getTotal={this.getTotalCount}
              name={nameAndCount.name}
              count={nameAndCount.count}
              key={i}
            />
          );
        })}
        <h1>Total Count: {this.state.total}</h1>
      </div>
    );
  }
}

export default App;

And Here is SubComp.js

import React, { Component } from 'react';
export default class SubComp extends Component {

  calculateTotal = () =>{
    this.props.getTotal(this.props.count);
  }

  render() {
    return (
      <div>
        <p onClick={this.calculateTotal}> Name: {this.props.name} || Count: {this.props.count}</p>
      </div>
    )
  }
};

Try to implement above and you will get exact scenario that how pass parameters works in reactjs on any DOM method.


U
Umair Ahmed

There are couple of ways to pass parameter in event handlers, some are following.

You can use an arrow function to wrap around an event handler and pass parameters:

<button onClick={() => this.handleClick(id)} />

above example is equivalent to calling .bind or you can explicitly call bind.

<button onClick={this.handleClick.bind(this, id)} />

Apart from these two approaches, you can also pass arguments to a function that is defined as a curry function.

handleClick = (id) => () => {
    console.log("Hello, your ticket number is", id)
};

<button onClick={this.handleClick(id)} />

S
SlimSim

I wrote a wrapper component that can be reused for this purpose that builds on the accepted answers here. If all you need to do is pass a string however, then just add a data-attribute and read it from e.target.dataset (like some others have suggested). By default my wrapper will bind to any prop that is a function and starts with 'on' and automatically pass the data prop back to the caller after all the other event arguments. Although I haven't tested it for performance, it will give you the opportunity to avoid creating the class yourself, and it can be used like this:

const DataButton = withData('button')

const DataInput = withData('input');

or for Components and functions

const DataInput = withData(SomeComponent);

or if you prefer

const DataButton = withData(<button/>)

declare that Outside your container (near your imports)

Here is usage in a container:

import withData from './withData';
const DataInput = withData('input');

export default class Container extends Component {
    state = {
         data: [
             // ...
         ]
    }

    handleItemChange = (e, data) => {
        // here the data is available 
        // ....
    }

    render () {
        return (
            <div>
                {
                    this.state.data.map((item, index) => (
                        <div key={index}>
                            <DataInput data={item} onChange={this.handleItemChange} value={item.value}/>
                        </div>
                    ))
                }
            </div>
        );
    }
}

Here is the wrapper code 'withData.js:

import React, { Component } from 'react';

const defaultOptions = {
    events: undefined,
}

export default (Target, options) => {
    Target = React.isValidElement(Target) ? Target.type : Target;
    options = { ...defaultOptions, ...options }

    class WithData extends Component {
        constructor(props, context){
            super(props, context);
            this.handlers = getHandlers(options.events, this);        
        }

        render() {
            const { data, children, ...props } = this.props;
            return <Target {...props} {...this.handlers} >{children}</Target>;
        }

        static displayName = `withData(${Target.displayName || Target.name || 'Component'})`
    }

    return WithData;
}

function getHandlers(events, thisContext) {
    if(!events)
        events = Object.keys(thisContext.props).filter(prop => prop.startsWith('on') && typeof thisContext.props[prop] === 'function')
    else if (typeof events === 'string')
        events = [events];

    return events.reduce((result, eventType) => {
        result[eventType] = (...args) => thisContext.props[eventType](...args, thisContext.props.data);
        return result;
    }, {});
}

T
Tom Fuller

I have below 3 suggestion to this on JSX onClick Events -

Actually, we don't need to use .bind() or Arrow function in our code. You can simple use in your code. You can also move onClick event from th(or ul) to tr(or li) to improve the performance. Basically you will have n number of "Event Listeners" for your n li element. So finally code will look like this:

    {this.props.items.map(item =>
  • ...
  • )}
// And you can access item.id in onItemClick method as shown below: onItemClick = (event) => { console.log(e.target.getAttribute("item.id")); } I agree with the approach mention above for creating separate React Component for ListItem and List. This make code looks good however if you have 1000 of li then 1000 Event Listeners will be created. Please make sure you should not have much event listener. import React from "react"; import ListItem from "./ListItem"; export default class List extends React.Component { /** * This List react component is generic component which take props as list of items and also provide onlick * callback name handleItemClick * @param {String} item - item object passed to caller */ handleItemClick = (item) => { if (this.props.onItemClick) { this.props.onItemClick(item); } } /** * render method will take list of items as a props and include ListItem component * @returns {string} - return the list of items */ render() { return (
{this.props.items.map(item => )}
); } } import React from "react"; export default class ListItem extends React.Component { /** * This List react component is generic component which take props as item and also provide onlick * callback name handleItemClick * @param {String} item - item object passed to caller */ handleItemClick = () => { if (this.props.item && this.props.onItemClick) { this.props.onItemClick(this.props.item); } } /** * render method will take item as a props and print in li * @returns {string} - return the list of items */ render() { return (
  • {this.props.item.text}
  • ); } }


    This does not work when the data you need to pass is an object. The attribute will only work with strings. Also reading from the dom via get attribute is probably a more expensive operation.
    M
    Merugu Prashanth

    I have added code for onclick event value pass to the method in two ways . 1 . using bind method 2. using arrow(=>) method . see the methods handlesort1 and handlesort

    var HeaderRows  = React.createClass({
        getInitialState : function() {
          return ({
            defaultColumns : ["col1","col2","col2","col3","col4","col5" ],
            externalColumns : ["ecol1","ecol2","ecol2","ecol3","ecol4","ecol5" ],
    
          })
        },
        handleSort:  function(column,that) {
           console.log(column);
           alert(""+JSON.stringify(column));
        },
        handleSort1:  function(column) {
           console.log(column);
           alert(""+JSON.stringify(column));
        },
        render: function () {
            var that = this;
            return(
            <div>
                <div>Using bind method</div>
                {this.state.defaultColumns.map(function (column) {
                    return (
                        <div value={column} style={{height : '40' }}onClick={that.handleSort.bind(that,column)} >{column}</div>
                    );
                })}
                <div>Using Arrow method</div>
    
                {this.state.defaultColumns.map(function (column) {
                    return (
                        <div value={column} style={{height : 40}} onClick={() => that.handleSort1(column)} >{column}</div>
    
                    );
                })}
                {this.state.externalColumns.map(function (column) {
                    // Multi dimension array - 0 is column name
                    var externalColumnName = column;
                    return (<div><span>{externalColumnName}</span></div>
                    );
                })}
    
            </div>);
        }
    });
    

    P
    Pang

    Below is the example which passes value on onClick event.

    I used es6 syntax. remember in class component arrow function does not bind automatically, so explicitly binding in constructor.

    class HeaderRows extends React.Component {
    
        constructor(props) {
            super(props);
            this.handleSort = this.handleSort.bind(this);
        }
    
        handleSort(value) {
            console.log(value);
        }
    
        render() {
            return(
                <tr>
                    {this.props.defaultColumns.map( (column, index) =>
                        <th value={ column } 
                            key={ index } 
                            onClick={ () => this.handleSort(event.target.value) }>
                            { column }
                        </th>
                    )}
    
                    {this.props.externalColumns.map((column, index)  =>
                        <th value ={ column[0] }
                            key={ index }>
                            {column[0]}
                        </th>
                    )}
                </tr>
             );
        }
    }
    

    A
    Andysenclave

    I guess you will have to bind the method to the React’s class instance. It’s safer to use a constructor to bind all methods in React. In your case when you pass the parameter to the method, the first parameter is used to bind the ‘this’ context of the method, thus you cannot access the value inside the method.


    J
    Juan David Arce
    1. You just have to use an arrow function in the Onclick event like this: 
    
    <th value={column} onClick={() => that.handleSort(theValue)} >{column}</th>
    
    2.Then bind this in the constructor method:
        this.handleSort = this.handleSort.bind(this);
    
    3.And finally get the value in the function:
      handleSort(theValue){
         console.log(theValue);
    }
    

    M
    Mario Petrovic

    Using arrow function :

    You must install stage-2:

    npm install babel-preset-stage-2 :

    class App extends React.Component {
        constructor(props) {
            super(props);
            this.state = {
                value=0
            }
        }
    
        changeValue = (data) => (e) => {
            alert(data);  //10
            this.setState({ [value]: data })
        }
    
        render() {
            const data = 10;
            return (
                <div>
                    <input type="button" onClick={this.changeValue(data)} />
                </div>
            );
        }
    }
    export default App; 
    

    R
    Romia Mukherjee

    Theres' a very easy way.

     onClick={this.toggleStart('xyz')} . 
      toggleStart= (data) => (e) =>{
         console.log('value is'+data);  
     }
    

    A
    Anik Mazumder
    class TableHeader extends Component {
      handleClick = (parameter,event) => {
    console.log(parameter)
    console.log(event)
    
      }
    
      render() {
        return (
          <button type="button" 
    onClick={this.handleClick.bind(this,"dataOne")}>Send</button>
        );
      }
    }
    

    While this code may solve the question, including an explanation really helps to improve the quality of your post. Remember that you are answering the question for readers in the future, and those people might not know the reasons for your code suggestion.
    C
    Charitha Goonewardena

    Coming out of nowhere to this question, but i think .bind will do the trick. Find the sample code below.

    const handleClick = (data) => {
        console.log(data)
    }
    
    <button onClick={handleClick.bind(null, { title: 'mytitle', id: '12345' })}>Login</button>
    

    H
    Hiren Gohel

    There are 3 ways to handle this :-

    Bind the method in constructor as :- export class HeaderRows extends Component { constructor() { super(); this.handleSort = this.handleSort.bind(this); } } Use the arrow function while creating it as :- handleSort = () => { // some text here } Third way is this :- that.handleSort} >{column}


    T
    Tiw

    You can use your code like this:

    <th value={column} onClick={(e) => that.handleSort(e, column)} >{column}</th>
    

    Here e is for event object, if you want to use event methods like preventDefault() in your handle function or want to get target value or name like e.target.name.


    J
    Juan Lanus

    There were a lot of performance considerations, all in the vacuum. The issue with this handlers is that you need to curry them in order to incorporate the argument that you can't name in the props. This means that the component needs a handler for each and every clickable element. Let's agree that for a few buttons this is not an issue, right? The problem arises when you are handling tabular data with dozens of columns and thousands of rows. There you notice the impact of creating that many handlers.

    The fact is, I only need one. I set the handler at the table level (or UL or OL...), and when the click happens I can tell which was the clicked cell using data available since ever in the event object:

    nativeEvent.target.tagName
    nativeEvent.target.parentElement.tagName 
    nativeEvent.target.parentElement.rowIndex
    nativeEvent.target.cellIndex
    nativeEvent.target.textContent
    

    I use the tagname fields to check that the click happened in a valid element, for example ignore clicks in THs ot footers. The rowIndex and cellIndex give the exact location of the clicked cell. Textcontent is the text of the clicked cell.

    This way I don't need to pass the cell's data to the handler, it can self-service it. If I needed more data, data that is not to be displayed, I can use the dataset attribute, or hidden elements. With some simple DOM navigation it's all at hand. This has been used in HTML since ever, since PCs were much easier to bog.


    You raise a very important issue - Performance Consideration!
    y
    yfalik

    When working with a function as opposed to a class, it's actually fairly easy.

    
        const [breakfastMain, setBreakFastMain] = useState("Breakfast");
    
    const changeBreakfastMain = (e) => {
        setBreakFastMain(e.target.value);
    //sometimes "value" won't do it, like for text, etc. In that case you need to 
    //write 'e.target/innerHTML'
     }
    
    <ul  onClick={changeBreakfastMain}>
       <li>
    "some text here"
       </li>
    <li>
    "some text here"
       </li>
    </ul>
    

    f
    francis

    I'd do it like this:

    const HeaderRows = props => {
        const handleSort = value => () => {
    
        }
    
        return <tr>
            {props.defaultColumns.map((column, i) =>
                <th key={i} onClick={handleSort(column)}>{column}</th>)}
            {props.externalColumns.map((column, i) => {
                // Multi dimension array - 0 is column name
                const externalColumnName = column[0]
                return (<th key={i}>{externalColumnName}</th>)
            })}
        </tr>
    }