react/jsx-key is triggering false positive for props defined as an object properties

[awthwathje]

Sometimes it is useful to define a component call as

<Component {...{ key: id, id, shortTitle }} />

instead of

<Component key={id} id={id} shortTitle={shortTitle} />

but in the first case ESLint gets mad about the missing key prop, triggering the react/jsx-key rule.

This is the reason why I'm turning this rule off for now. I believe this should be fixed.

[ljharb]

This is actually intentional, and in a future version of React key I believe won't be possible to spread, it will only be allowed statically provided.

The key should always be hardcoded; it's not a normal prop.

[awthwathje]

Then I think it is good idea to explicitly mention this in the documentation.

[ljharb]

Sure, a PR to add that to the jsx-key docs would be great!

[awthwathje]

Duh... Well, okay. Will do it.