Skip to content

[Bug]: react/jsx-key rule is not applied when using return statement and ternary operator in iterator #3925

Open
@Dorianspeed

Description

@Dorianspeed

Is there an existing issue for this?

  • I have searched the existing issues and my issue is unique

Description Overview

Brief description

As described in the title, react/jsx-key is not applied when using return statement and ternary operator in iterator.
It's working when not using return statement as shown in my below picture.

Picture showing the current issue

Image

Code to reproduce error

Here is a small code snippet to reproduce the current error:

import { Fragment } from 'react';

const ITEMS = ['bar', 'foo'];

export default function BugIssue() {
  return (
    <Fragment>
      {ITEMS.map((item) => {
        return item === 'bar' ? <div>{item}</div> : <span>{item}</span>;
      })}
    </Fragment>
  );
}

Expected Behavior

An error should be displayed when using return statement and ternary operator.

=> Missing "key" prop for element in iterator

eslint-plugin-react version

v7.37.3

eslint version

9.27.0

node version

v22.15.0

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy