Chip: unique "key" prop warning

[nNBee]

Describe the bug

Warning: Each child in a list should have a unique "key" prop.

Check the render method of `Chip`. See https://reactjs.org/link/warning-keys for more information.
    at img
    at http://localhost:3000/node_modules/.vite/deps/primereact_chip.js?v=2ebc8c29:172:20

Reproducer

No response

System Information

System:
    OS: macOS 15.0.1
    CPU: (8) arm64 Apple M1
    Memory: 87.70 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.15.0 - ~/.nvm/versions/node/v20.15.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.15.0/bin/npm
  Browsers:
    Brave Browser: 112.1.50.121
    Chrome: 130.0.6723.69
    Safari: 18.0.1
  npmPackages:
    primereact: ^10.8.4 => 10.8.4 
    react: ^18.3.1 => 18.3.1

Steps to reproduce the behavior

No response

Expected behavior

No response

[melloware]

10.8.5 has not been released yet...

[nNBee]

10.8.5 has not been released yet...

Yes, by the time I wrote it down, I realized that the new release hadn’t come out yet. Sorry...

[melloware]

No worries!

[nNBee]

Hi, thank you for the previous fixes! However, with version 10.8.5, the issue still persists, but I believe it is in the “Chip” component, not the “Chips” component.

The problem lies in the createContent function, specifically here:

if (props.image) {
    const imageProps = mergeProps(
        {
            src: props.image,
            onError: props.onImageError
        },
        ptm('image')
    );

    content.push(<img alt={props.imageAlt} {...imageProps} />);

In the content.push line, the img element does not have a key prop. I believe this is what causes the “Each child in a list should have a unique ‘key’” warning.

[melloware]

Yep I see it fixing it now.