React does not recognize the inputRef prop on a DOM element

[Mustafa-Agha]

When I try to use react-json-view to render expandable row in a functional component in a table I get this error when I use onEdit method

React does not recognize the inputRef prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase inputref instead. If you accidentally passed it from a parent component, remove it from the DOM element

code

import { Table } from 'antd';

const columns = [
  {
    title: 'ID',
    dataIndex: 'id',
  }
];

<Table
  rowKey="id"
  columns={columns}
  dataSource={data}
  expandable={{
    expandedRowRender: (record) => (
      <ExpandedRow record={record} />
    ),
  }}
/>;

//ExpandedRow child component

import { FC } from 'react';
import ReactJson from 'react-json-view';

interface IExpandedRow {
  record: any;
}

const ExpandedRow: FC<IExpandedRow> = ({ record, ...rest }: IExpandedRow) => {
  const onEdit = (data: any) => {
    console.log(data);
  };

  return (
    <>
      <ReactJson
        {...rest}
        onEdit={onEdit}
        src={record}
      />
    </>
  );
};

export default ExpandedRow;

I tried to create ref and pass it to ExpandedRow component but I got the same error, am I doing something wrong here ?

[benpingilley]

Experiencing the same issue.

[raptoria]

+1

[mddarmawan]

Same here.

[AaryanAdil]

+1

[samsungapore]

having the same issue (using Next.js)

[enricomad]

duplicate of #347

[laolaolulu]

+1

[kulabros]

+1 .... When I try rjv demo, there's no warning on json editing start. In my application, when I try te edit any element, I got this warning in the time I click to edit icon. I can't recognise the main difference in my vs. demo code, which causes this warning.. Thanks for any help

[enricomad]

@kulabros the issue is triggered by newer versions of react (compared to demo code), which the lib is not compatible with anymore.
more details in #347

[dranitski]

upvote the fix by @enricomad #374 🆙

[RodrigosTiago]

Same problem here until today :D Do I have to do anything to fix it?