While using the table shorthand, if there is repeating data between two different columns/cells in the same row, then it triggers the react duplicate key warning. The row itself is given a key, but the cell is automatically generated by the content.

As far as I can tell this is a different issue than #1205 which was for the table row itself. It might be the same as #1030, but that was closed with the assumption that it was addressed by #599.

I am not sure if any of these took into the consideration the possibility of the data itself matching, so I thought it was important to report. If there is matching data on different rows, then the warning is not triggered.

Starting with the standard table example I modified the data slightly to have two of the data cells be an exact match.

const tableData = [
  {
    name: undefined,
    status: "repeat",
    notes: "repeat",
    key: "1"
  },
  {
    name: "Jimmy",
    status: "Requires Action",
    notes: undefined,
    key: "2"
  },
  {
    name: "Jamie",
    status: undefined,
    notes: "Hostile",
    key: "3"
  },
  {
    name: "Jill",
    status: undefined,
    notes: undefined,
    key: "4"
  }
];

Simplest form of renderBodyRow causes the duplicate key warning to appear:

const renderBodyRow = ({ name, status, notes, key }) => ({
    key: key,
    warning: !!(status && status.match("Requires Action")),
    cells: [
        name || "No name specified", 
        status || "Unknown", 
        notes || "None"
    ]
});

If the content of the cell is modified then the error will not be triggered:

const renderBodyRow = ({ name, status, notes, key }) => ({
    key: key,
    warning: !!(status && status.match("Requires Action")),
    cells: [
        name || "No name specified",
        <Header icon="warning" content={status} /> || "Unknown",
        notes || "None"
    ]
});

If both of the cells have the same content then again the warning is triggered:

const renderBodyRow = ({ name, status, notes, key }) => ({
    key: key,
    warning: !!(status && status.match("Requires Action")),
    cells: [
          name || "No name specified",
          status ? <Header icon="warning" content={status} /> : "Unknown",
          notes ? <Header icon="warning" content={notes} /> : "none",
    ]
});

Since the table cells within a row are siblings, I believe that the error itself is accurate. Can the automatically generated key possibly include the header row or something else that will ensure it is unique? This would allow for using the most basic option for renderBodyRow.

react 16.8.0
react-dom 16.8.0
semantic-ui-react 1.2.0

example created:
https://codesandbox.io/s/suir-table-shorthand-keys-2t2bt